CI/CD·Pushed May 1, 2026·S

CI workflow strips Pages deployment pending repo public launch

The GitHub Actions workflow has been reconfigured to handle a phased deployment approach — builds run and artifacts are uploaded, but Pages deployment stays disabled until the repository flips public.

GitHub Pages deployment isn't available on private repositories for free, Pro, or Team plans. The workflow now runs only the build step and uploads the output as a standard artifact, keeping Pages deployment commented out until the repo goes public. Once that happens, a single commented block needs to be uncommented to restore the full build-and-deploy pipeline. Permissions have been tightened to just [[code]].github/workflows/analyze.yml[[/code]] read access, and artifact retention is capped at 7 days to avoid cluttering storage.

Technical description

The workflow file has been restructured for a phased deployment approach. The primary build job now only runs the build and uploads the output using [[code]]actions/upload-artifact@v4[[/code]] instead of the Pages-specific upload step. Permissions have been reduced from [[code]]contents: write, pages: write, id-token: write[[/code]] down to [[code]]contents: read[[/code]] only — the build step doesn't need write access. A commented-out [[code]]deploy-pages[[/code]] job is included to show exactly what needs to be uncommented once the repository becomes public. That job has its own permissions block ([[code]]pages: write, id-token: write[[/code]]) and includes the Pages environment configuration. For now, it's dormant code waiting for Phase 1. Artifact retention was explicitly set to 7 days rather than relying on the default 30-day retention — keeping artifact storage lean during the private-repo period. The overall scope is confined to CI configuration, with no changes to application code or build tooling.