Skip to content

feat: publish via gh-pages-fork (release 4.0.0-rc.0) - #218

Open
JohannesHoppe wants to merge 25 commits into
mainfrom
feat/gh-pages-fork
Open

JohannesHoppe wants to merge 25 commits into
mainfrom
feat/gh-pages-fork

Conversation

@JohannesHoppe

@JohannesHoppe JohannesHoppe commented Oct 9, 2026 •

Copy link
Copy Markdown
Member

Closes #215. See also #90.

Release 4.0.0-rc.0 (then 4.0.0). Supports Angular 18 to 22 and Node.js >= 18.19.1, as before. A major version because the publish step is rewritten and some results change on purpose (listed below); setups that worked with 3.1.2 keep working, apart from those deliberate changes.

What

src/gh-pages-fork/ is a minimal TypeScript fork of gh-pages (base: main at 48f62a7), set up like commander-fork: it exists solely for angular-cli-ghpages and will never be a general-purpose library. It keeps the upstream file structure and function names (lib/index.ts, lib/git.ts, lib/util.ts), so upstream changes can be compared and ported file by file. Its README lists the base commit, what was kept, added and removed, and every deviation from upstream.

How a deploy works

  1. checks before anything is cloned (the same ones run in --dry-run): the directory exists and contains files, it isn't a project root (a .git entry and a package.json, while dotfiles are published), --branch and --message aren't empty; stale temporary clones of interrupted deploys are removed
  2. git ls-remote, run in a throwaway repository with the remote (so includeIf sections of the user's config apply, the project's git config doesn't), checks the target branch: an existing branch is cloned alone, without checkout; a new branch starts as an empty repository in the object format of the remote
  3. .nojekyll is written, the build is copied (without .git), then CNAME (--cname replaces a CNAME of the build) and 404.html (copy of index.html)
  4. a warning lists the files an ignore rule matches; git add --force --all (with --add: read-tree HEAD + --ignore-removal); a warning lists the env files in the index; commit if something changed, push refs/heads/<branch>; the clone's info/attributes unsets all content conversions, so every file is published byte for byte
  5. the temporary directory is removed; a failing removal is logged and never changes the result

The git directory (.git) lives next to the work tree in a private temporary directory, so no file of the build can overwrite it; a .git file in the work tree points to it, so a git launcher that drops GIT_DIR (wslgit, sudo) still finds the clone. Commands on the clone run with GIT_DIR/GIT_WORK_TREE pinned, inherited repository variables are removed. A password in the repository URL disables credential helpers; userinfo in an http(s) URL is removed from the clone's remote config right after cloning and passed to push on the command line; logs and the dry-run output hide it.

Env files: published, with a warning

As in 3.1.2, env files in the build are published like every other file: someone who puts one into the build may intend it. Every deploy (also --dry-run) lists .env, .env.*, *.env (any case, any folder, also folders with such a name) in a warning, also those that --add keeps from the branch. The warning goes through logger.warn and has an emoji: ng deploy shows it in bold yellow, the standalone CLI now does the same for all its warnings (respecting NO_COLOR/FORCE_COLOR).

What protects against publishing the project's own .env by accident is the check of the directory: an empty --dir is an error, and a directory with a .git entry and a package.json (a project root) is refused while dotfiles are on. CI deploys a build with a .env for every Angular version and on every platform and checks the warning.

Differences from 3.1.2

From three max-effort reviews (the last one ran 3.1.2 and this build side by side in about 250 scenarios). Every item has a regression test, most with real git.

Bug fixes (3.1.2 failed or did something unintended)

  • concurrent deploys (e.g. nx run-many -t deploy) deleted or shared each other's clone; worst case, git commands ran in the user's project repository
  • a deploy started by git (hooks, ! aliases, worktrees) inherited GIT_DIR/GIT_INDEX_FILE and acted on the user's repository
  • the first deploy with --add to a new branch published the default branch's source tree
  • one transient error on the first clone turned an existing branch into an orphan and the push was rejected
  • a submodule gitlink sorting before .gitmodules (e.g. .github/actions/x) made every deploy fail
  • tracked dotfiles matching an ignore rule were deleted from the site
  • a dangling .nojekyll symlink on the branch made --add create its target outside the clone; a symlinked dist/404.html overwrote its target outside the build
  • a git process killed by a signal (OOM, watchdog) counted as success
  • stderr output of git (e.g. GIT_TRACE) was read as repository URL or commit user
  • a missing git binary and real git config errors were reported as a missing remote
  • relative repository paths (--repo=../pages.git, or from the git config) failed
  • the token stayed in the cached clone's .git/config (and in the directory name of 3.x clones)
  • a second deploy with --no-notfound still published the 404.html that an earlier deploy had written into a reused dist
  • an unchanged redeploy of a build with a top-level HEAD folder failed ("nothing to commit")
  • a build folder that is a clone of the pages branch failed to deploy
  • a symlink cycle in the build was published as 32 nested copies, two cycles ran out of memory; dot-named symlinks (.htaccess → …) were dropped on every second deploy; a nested repository was published as an empty gitlink instead of its files
  • a read-only node_modules made every deploy fail (now: os temp directory); a tag named like the target branch made the deploy fail (the push now names refs/heads/<branch>)
  • --add with a file/folder name conflict between build and branch failed with EEXIST (now the build wins; the replaced branch files are logged)
  • standalone CLI: --add=false turned add mode on, --dry-run=false still ran a dry run, absolute --dir paths didn't work, and npx angular-cli-ghpages crashed on Node 18 with a fresh install (ERR_REQUIRE_ESM)
  • ng deploy from a subdirectory looked for the build output relative to the current working directory instead of the workspace root
  • the --no-silent deprecation warning appeared on every ng deploy
  • deploy/schema.d.ts was missing from the package (the published typings import it)
  • GitHub Enterprise Server: the commit link in the commit message pointed to github.com
  • re-running ng add failed with "Target name already exists"
  • --dry-run passed setups that the deploy then refused (project root, empty directory, --dir pointing at a file, empty --branch or --message), left out the ignore-rule warning, promised a 404.html without an index.html and a commit author for --name without --email
  • --cname lost silently against a CNAME file of the build (e.g. public/CNAME), while the log said "Creating CNAME for …"
  • a string outputPath of the browser builders (@angular-devkit/build-angular:browser, :browser-esbuild, @angular-builders/custom-webpack:browser, …) got a /browser suffix, so the deploy didn't find the build
  • --dir=missing outside a git repository reported a missing remote instead of the missing directory
  • ng deploy --help described the noX options with the opposite meaning of the flag it shows (--dotfiles Exclude dotfiles … [default: false])

Deliberate behavior changes

  • ignore rules don't decide what is published: every file of the build is published (except .git), also files that the deploying machine's global gitignore or a .gitignore in the build matches. 3.1.2 left them out silently, so the result depended on the machine. A warning now lists these files.
  • the build folder is never modified: 404.html goes into the deployment only. A pipeline that reuses dist after ng deploy (e.g. uploads it elsewhere) no longer finds a 404.html there.
  • --name/--email win over GIT_AUTHOR_*/GIT_COMMITTER_* from the environment (git hooks and some CI systems export them).
  • --cname replaces a CNAME file of the build (3.1.2 published the build's file).
  • every file is published byte for byte: .gitattributes (of the build or the user), core.autocrlf and LFS filters don't change the content any more (3.1.2 applied them on git add, e.g. CRLF → LF on Windows with core.autocrlf=true). The first deploy after the upgrade can create one extra commit for such files.
  • project roots are refused: an empty --dir is an error; a directory with a .git entry and a package.json is refused while dotfiles are on (--no-dotfiles allows it).

New warnings and messages (results unchanged)

  • env files in the deployment (.env, .env.*, *.env), also in --dry-run
  • files matching an ignore rule (see above)
  • standalone CLI: warnings in bold yellow on a terminal (Node.js rules for FORCE_COLOR, NO_COLOR, TERM=dumb); positional arguments are ignored with a warning; -S/--no-silent prints the deprecation warning on stderr
  • the log lists removed files (at most 10 names); gh-pages' lines (Cleaning, Fetching origin, Checking out …) are gone
  • ng add explains an existing deploy target of another builder and keeps its own one, and takes the project of the current directory
  • --base-href with --no-build warns that it has no effect
  • a push rejected by a concurrent deploy says so and suggests running the deploy again; error messages name --dir, --repo, --branch, --message

Other differences (served site unchanged)

  • file modes: files are written as 100644; an executable on the branch that the build overwrites becomes 100644, a non-empty .nojekyll becomes empty, a symlink on the branch overwritten with --add becomes a file. The first deploy after the upgrade can therefore create one extra commit.
  • every deploy uses a fresh temporary clone, removed at the end (no reused cache clone)
  • --dry-run lists the build and reads its ignore rules (in a throwaway repository with the build as work tree), without contacting the remote
  • standalone CLI: --flag=false (also 0, no, off) leaves a boolean flag unset; negated flags with a value (--no-dotfiles=false) behave as in 3.1.2

For the release notes

  • the transitive gh-pages package and its tree (about 40 packages, e.g. fs-extra, globby, commander@13) and the gh-pages/gh-pages-clean bins are gone; projects that use them through angular-cli-ghpages must add them themselves
  • programmatic API: Schema/PreparedOptions are real types now (deploy/schema.d.ts was missing), stricter TypeScript can flag code that compiled before; internal deep exports are gone (setupMonkeypatch, GHPages/PublishOptions/GhPagesGit types, getRemoteUrl, ensureGhPagesCacheDir, cleanupMonkeypatch, collectDistFiles, createCleanupBeforeAddHook)
  • ignore rules, --cname over a build's CNAME, byte-for-byte content and the dist/404.html (see above)
  • docs: --build-target takes a full target string (project:build:configuration); PERSONAL_TOKEN/GITHUB_TOKEN are injected into plain https://github.com/ URLs, the GH_TOKEN placeholder only takes GH_TOKEN; unknown options in angular.json are ignored

Tests

  • npm test type-checks all sources including specs; a vitest setup isolates the git environment (no global/system config, no inherited repository variables, tokens or CI variables); test files run in parallel
  • src/test-helpers/git.ts: shared real-git helpers and one spawn mock for the behavior and git-command specs
  • real-git specs use file:// remotes (shallow clones are real) and bare repositories with main as default branch
  • the gh-pages specs are ported to the fork instead of deleted; the behavior spec's done callbacks (which Vitest ignores, so its tests passed regardless of their assertions) are async
  • the standalone CLI deploys for real in a spec
  • CI installs the packed package fresh on Node 18.19.1, 20, 22, 24 (Ubuntu) and on macOS and Windows: require, import, builder and real standalone deploys including env files and their warning, --add redeploy, empty --dir and project root; besides ng new → ng add → ng deploy with a .env in the build for Angular 18 to 22 (published, warning in the output)
  • npm test builds first

Also: vitest.config.ts → .mts, commander-fork fixes 3/4 (boolean flags with a value) and 4/4 (opts() leaves an unset --name undefined instead of returning the name() method, needed since the CLI passes opts() to the engine), docs for the fork and for watching upstream gh-pages.

Vitest 5 warns about ESM syntax in a config file loaded as CommonJS.
src/gh-pages-fork is a minimal TypeScript fork of gh-pages (base: main at 48f62a7), internal to angular-cli-ghpages, with the upstream file structure and function names (lib/index.ts, lib/git.ts, lib/util.ts). It uses async/await throughout, has no dependencies and keeps only the options angular-cli-ghpages passes.

This removes all workarounds around gh-pages:
- the util.debuglog monkeypatch (the fork takes a log callback)
- the CACHE_DIR fallback for directories without package.json (#203)
- the beforeAdd cleanup hook (#204/#217); the fork removes all tracked files with git rm before copying dist
- the callback-to-promise bridge (#205); publish() rejects on every error
- the type declarations for gh-pages/lib/git

Removes the gh-pages dependency and its tree (48 packages, including the braces advisory CVE-2026-93687). Deploy results are unchanged: 14 real-git scenarios (first deploy, redeploy, seeded branch with dotfiles and submodule, --add, --no-dotfiles, user handling, symlinks, push rejection, dry run, --remote) produce identical branches, commits and exit codes with 3.1.2 and this build.

setupMonkeypatch and the GHPages/PublishOptions types stay exported as deprecated for API compatibility.

Closes #215
No external code depends on them, so they don't need to stay as deprecated exports.
The behavior, clean, cleanup, file creation, integration and no-package-json specs pin the deploy behavior, so they now run against gh-pages-fork with their expectations unchanged where the behavior is the same. Tests that only demonstrated upstream gh-pages bugs are dropped.

The behavior spec used done callbacks, which Vitest doesn't support: the first parameter is the test context, so these 24 tests passed regardless of their assertions. They are async now and fail on a wrong expectation.
- every publish() clones into a fresh temporary directory below the cache directory and removes it afterwards: concurrent deploys no longer delete or share each other's clone, no token stays in .git/config, and the engine no longer wipes the shared cache
- GIT_CEILING_DIRECTORIES keeps git inside the clone, so a broken clone can never fall through to the user's project repository
- credential helpers are disabled for repository URLs that carry credentials
- the remote url mismatch check is gone (every clone is fresh), so relative repository paths work
- git rm removes .gitmodules before all other files, so a submodule gitlink sorting before it (e.g. .github/actions/x) no longer breaks every deploy
- a new branch starts as an empty orphan branch, so the first deploy with --add no longer publishes the default branch's source tree
- spawn() rejects unless the exit code is 0 (a git process killed by a signal no longer counts as success) and returns stdout only
- getRemoteUrl() rethrows errors other than a failed git config, so a missing git binary is reported as such
- listFiles() skips broken symlinks and symlink cycles
- copy() writes files without the executable bit (like gh-pages v6.3.0), creates every directory once and copies with limited concurrency
- getUser() uses the configured git executable
- the fork's MIT license ships in the package
- real-git regression tests for every fix in gh-pages-fork publish()
- the clean spec checks that the temporary clone is removed after successful and failed deploys
- file creation tests check the pushed branch instead of the clone
- the dry-run 404.html test is restored (it was merged with a cname test)
- behavior and integration specs clear token variables and describe the fork instead of gh-pages internals
- npm test type-checks all sources including specs; spec type errors are fixed
- test files run in parallel again (no shared cache between suites)
- a non-writable cache directory (e.g. a read-only node_modules) falls back to a clone directory in the os temp dir
- when the target branch doesn't exist yet, the default branch is cloned shallow and without a checkout (only the remote is needed), with a full clone as the last resort for servers without shallow clone support
- src/test-helpers/git.ts: git(), tree(), commitCount(), createBareRepo(), seedBranch(), createMockChildProcess()
- real-git specs use the shared helpers instead of their own git wrappers and seed code
- the behavior spec configures responses through one spawnOverride hook instead of three copies of the spawn mock
- engine.spec no longer repeats the publish error handling of the integration spec
- tests for the temp dir and full clone fallbacks
@JohannesHoppe

Copy link
Copy Markdown
Member Author
VID-20260901-WA0006.mp4

…the user's repository

- git ls-remote decides whether the branch exists: an existing branch is cloned (shallow, then in full), a new branch starts as an empty repository. A transient error on the first clone no longer turns an existing branch into an orphan, hard failures report the real git error after one attempt, and the default branch is never checked out
- the branch is cloned without a checkout and staged with git add --force --all (--ignore-removal plus read-tree HEAD with --add): no git rm, so .gitmodules, ignore rules (global gitignore, .gitignore in dist) and symlinks on the branch can no longer drop or redirect files
- commands for the clone run with GIT_DIR/GIT_WORK_TREE pinned to it, without inherited repository variables (hooks, aliases, worktrees) and with safe.directory for it
- credential helpers are only disabled for URLs with a password; a URL with only a username (Bitbucket, Azure DevOps) keeps using them
- the token is removed from the clone's remote config right after cloning and only passed to push on the command line
- a failing cleanup of the temporary clone is logged instead of replacing the deploy result
- stale clones of interrupted deploys and clones of older versions are removed before each deploy; without a cache directory, clones go to a private directory in the os temp dir
- relative repository paths are resolved before cloning (from git config: against the repository top level)
- commits skip hooks (--no-verify); signal kills keep git's output in the error; getRemoteUrl reports real git errors
- listFiles skips .git and uses the JavaScript realpath
- shared spawn mock and git helpers for the specs
- commander-fork: boolean flags accept =true/=false (--add=false turned add mode on, --dry-run=false still ran a dry run)
- standalone CLI: unexpected positional arguments are an error (a directory argument was silently ignored); --dir accepts absolute paths
- utils.ts loads @angular-devkit/schematics only in createHost, so the engine and the standalone CLI run on Node 18 with a fresh install
- ng deploy resolves the auto-detected output directory against the workspace root instead of the current working directory
- an existing 404.html in dist is kept instead of being overwritten with index.html
- the dry-run output hides credentials of the repository URL
- the GitHub Actions commit link in the commit message uses GITHUB_SERVER_URL (GitHub Enterprise Server)
- the --no-silent deprecation warning only appears when the option is passed (schema without default; standalone CLI --no-silent)
- ng add keeps an existing angular-cli-ghpages deploy target and explains an existing deploy target of another builder; the workspace write is awaited
- deploy/schema.d.ts ships with the package (the published typings import it)
- remote URL discovery uses gh-pages-fork getRepo directly
…I on all Node versions

- vitest setup: empty global git config, no system config, no inherited repository variables, tokens or CI variables
- real-git tests use file:// remotes (shallow clones are real) and bare repositories with main as default branch
- new real-git tests: more files than the copy concurrency, nested dotfiles and .well-known, non-default remote, transient shallow clone failure keeps history, global gitignore, basePath that is a file, git identity from the environment, stale clone removal, failing cleanup (separate spec)
- standalone CLI: argument validation, --add=true/false, absolute --dir and a real deploy
- engine: kept 404.html, dry-run token redaction, GitHub Enterprise links, --no-silent of the standalone CLI, exact error preservation, ng add with an existing deploy target
- commander-fork: tests for boolean flags with a value
- behavior and git-commands specs share one spawn mock
- CI: the packed package is installed fresh and deploys with the standalone CLI on Node 18.19.1, 20, 22 and 24
publish() copies index.html to 404.html in the clone before copying the build, so a 404.html of the build wins and the build folder is never modified. A 404.html generated by an earlier deploy can no longer go stale in a reused dist folder or be published despite --no-notfound.
- fork README: structure, kept/added/removed parts and every deviation from upstream
- CLAUDE.md: deployment flow, standalone CLI, output directory resolution, watching upstream gh-pages
- README and standalone docs: dotfiles and ignore rules, 404.html, --add, --dir
- contributor docs: compiling programmatic usage examples, watching the forks, version list
- tests for 404.html in the deployment, remove an unused spy
@JohannesHoppe JohannesHoppe changed the title feat: publish via gh-pages-fork instead of the gh-pages package feat!: publish via gh-pages-fork (release 4.0.0) Oct 12, 2026
- deploy commits run git hooks again (no --no-verify): there is no reported problem it would fix
- commander-fork: --flag=false leaves a boolean flag unset; every other value sets it, as before
- standalone CLI: positional arguments are ignored with a warning instead of failing the deploy
- Git.exec() resolves with stdout; the mutable output field is gone
No user-facing breaking changes, so the fork ships as a minor version: everyone on ^3 gets the dependency-free publish step and its fixes.
@JohannesHoppe JohannesHoppe changed the title feat!: publish via gh-pages-fork (release 4.0.0) feat: publish via gh-pages-fork (release 3.2.0-rc.0) Oct 14, 2026
…files

Security
- env files (.env, .env.*, *.env, any case, any folder) are never published: skipped when listing the files and removed from the index before every commit, also when --add keeps them from the branch
- an empty --dir is an error, and a directory with a .git entry is refused when dotfiles are published, so a project root can't be published by accident
- the git directory lives next to the work tree in the private temp directory, so no file of the build can overwrite it (.GIT/config on case-insensitive file systems); .git is skipped in any case
- token as username (https://TOKEN@github.com/...): the URL is stripped from the clone's config, too
- redact() and the credential checks work on the raw string, so they also cover URL forms new URL() doesn't parse
- temp directories of 3.1.x in the os temp dir are removed

Regressions of the fork
- an unchanged redeploy with --add failed: commit() compares the index with HEAD (--cached)
- ls-remote ran in the user's repository and used its config (the extraheader of actions/checkout broke cross-repo deploys to private repositories, a broken .git file failed)
- a relative CACHE_DIR/TMPDIR failed: the clone directory is absolute
- a new branch took the user's default object format: it takes the remote's now
- 404.html is written after the copy, like 3.1.2 replacing a 404.html of the build (--no-notfound publishes that one) and without the mode of index.html
- removed files are logged again

Standalone CLI and package
- the package entry point loads on every supported Node version: ng-add.ts loads schematics lazily
- --dir=/x stays relative to the cwd if that path exists, otherwise it's absolute
- --flag=false also understands False, 0, no, off; --version=false prints the version
- generic warning for stray arguments; the engine gets plain options instead of the commander object

Other
- transient shallow clone failures retry shallow before falling back to a full clone, and are logged
- --name/--email override GIT_AUTHOR_*/GIT_COMMITTER_* from the environment
- no git maintenance in the throwaway clone
- $ patterns in tokens stay literal
- LICENSE of the package and of commander-fork ship in the package

CI and tests
- new package job: require, import, builder and a real deploy on Node 18.19.1, 20, 22, 24, on macOS and Windows; env files, --add redeploy, empty --dir and project root are checked there
- every Angular version deploys a build with a .env and checks that it's missing
- npm test builds first, so the CLI specs never run against a stale dist
- vitest setup also isolates identity and config variables and XDG_CONFIG_HOME and removes its temp dir
- real-git tests for every fix

Docs: fork README, CLAUDE.md, README and standalone docs describe the current behavior
…--name unset in opts()

Env files in the build are published again like every other file, as in 3.1.2:
someone who puts one into the build may intend it. Every deploy (also --dry-run)
lists them in a warning via logger.warn, bold yellow with an emoji in ng deploy
and in the standalone CLI (NO_COLOR/FORCE_COLOR respected). With --add, env
files already on the branch stay there and are listed, too. The protection
against publishing a project root (empty --dir, directory with .git) stays.

commander-fork: opts() returned the Command.prototype.name method for an unset
--name, so --email alone produced a git identity with a function as name
(FORK FIX 4/4).

Compared against 3.1.2 with real git: env scenarios (default, --no-dotfiles,
--add, redeploy) produce identical branches.
From a max-effort review against 3.1.2, each case compared side by side with
the published 3.1.2 and covered by a test:

- ls-remote runs in a throwaway repository with the remote, so includeIf
  sections of the user's config (per-account SSH key, insteadOf, proxy) apply
  like they do for clone and push; the clone's git directory is named .git, so
  includeIf "gitdir:**/.git" patterns match
- the work tree keeps a .git file (gitdir: ../.git): a git launcher that drops
  GIT_DIR/GIT_WORK_TREE (wslgit, sudo) still works on the clone and never on
  the project
- `--` after HEAD in diff-index: a HEAD/head folder in the build no longer
  breaks every redeploy; removed files are listed via diff-index (no rename
  detection, which took seconds and hid removals), at most 10 names per line
- a 404.html folder or a missing index.html never fails the deploy; the
  404.html copy reads index.html like 3.1.2 (Index.html on case-insensitive
  file systems)
- a warning lists the files an ignore rule matches (they are published)
- project root refusal needs .git and package.json: a build folder that is a
  clone itself deploys as in 3.1.2
- commander-fork: negated flags with a value (--no-dotfiles=false) set the
  flag as in 3.1.2
- an empty user name keeps the name of the git config
- the dry-run env warning never fails a dry run; listFiles needs realpath
  only for the base and symbolic links (large prerendered builds)
- ng add: require instead of import() for @angular-devkit/schematics, which
  works in the Angular CLI's schematic wrapper (NG_SCHEMATIC_REDIRECT)
- standalone CLI colors follow Node.js (FORCE_COLOR=0/false, NO_COLOR, TERM=dumb)

Cleanups: cloneBranch retry loop, dead dry-run fallback text, test literals
and helpers, comments and docs.
… bytes, docs match the code

Fixes from the review of documented against real behavior:
- --dry-run runs the checks of a deploy that need no clone (directory, project root,
  empty directory, empty --branch/--message) and shows the ignore-rule warning; it names a
  missing index.html and no longer promises an author for --name without --email
- --cname replaces a CNAME file (or folder) of the build; without --cname the build's CNAME is published
- every file is published byte for byte: info/attributes of the clone unsets text, eol,
  filter, ident and working-tree-encoding (.gitattributes, core.autocrlf, LFS filters)
- a push rejected by a concurrent deploy gets a hint to run the deploy again
- a missing build directory is reported before the remote lookup; error messages name --dir and --repo
- string outputPath of browser builders (*:browser, *:browser-esbuild, *-browser) is used as it is
- --base-href with --no-build warns that it has no effect
- ng add takes the project of the current directory
- schema and CLI help texts read correctly as --x and --no-x (ng deploy --help shows the
  noX options as --x); the misleading default: false of the noX options is removed
- README, standalone and GitHub Actions docs: --build-target is a full target string,
  --no-build still uses the build target, --remote section, token rules (PERSONAL_TOKEN
  only for plain github.com URLs, the GH_TOKEN placeholder only from GH_TOKEN), GITHUB_TOKEN
  note, includeIf in the temp directory, short flags, ngh, unknown options are ignored;
  Ionic example removed

Version 4.0.0-rc.0: a major release for the publishing rewrite of this branch.
@JohannesHoppe JohannesHoppe changed the title feat: publish via gh-pages-fork (release 3.2.0-rc.0) feat: publish via gh-pages-fork (release 4.0.0-rc.0) Nov 11, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove dependency on gh-pages

1 participant