This is an automated email from the ASF dual-hosted git repository.
hainenber pushed a change to branch
fix/resolve-oom-issues-when-building-docs-with-docusaurus-faster
in repository https://gitbox.apache.org/repos/asf/superset.git
discard 9a4dcabb6e4 chore: try to clean Netlify cache with `yarn clear` before
buillding
discard da77765a729 chore: try to clean Netlify cache before buillding
discard 6c1a3b7730a fix(ci): revert SWC usage when building docs
discard 28682119a2e fix(ci): correct Netlify config to set NODE_OPTIONS env var
add a6a93cde0ff fix(ci): correct Netlify config to set NODE_OPTIONS env var
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (9a4dcabb6e4)
\
N -- N -- N
refs/heads/fix/resolve-oom-issues-when-building-docs-with-docusaurus-faster
(a6a93cde0ff)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
docs/docusaurus.config.ts | 2 +-
docs/netlify.toml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
