Auto-enable Pages on first deploy#1445
Closed
bmehta001 wants to merge 1 commit into
Closed
Conversation
The GitHub Pages site has never been provisioned for this repository, so the post-merge deploy job in deploy-docs-pages.yml fails when actions/configure-pages@v5 looks up the site and gets a 404 (HTTP Not Found from the Pages API). Pass `enablement: true` to actions/configure-pages so the action provisions the Pages site on first run instead of erroring out. The workflow already grants the `pages: write` and `id-token: write` permissions that the action needs to do this. If the org-level GITHUB_TOKEN restrictions still prevent automatic enablement, a repository admin only needs to flip Settings -> Pages -> Build and deployment -> Source to `GitHub Actions` once; subsequent deploys will then succeed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the GitHub Pages deploy workflow to automatically provision/enable the repository’s Pages site on the first successful deployment, addressing current Get Pages site failed / 404 failures when Pages hasn’t been configured yet.
Changes:
- Pass
enablement: truetoactions/configure-pages@v5in the deploy job so the action can auto-enable Pages on first run.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
lalitb
reviewed
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
enablement: truetoactions/configure-pages@v5so the Deploy documentation to GitHub Pages workflow provisions the Pages site on first run.Why
The post-merge deploy job has been failing on every push to
mainwith::gh api repos/microsoft/cpp_client_telemetry/pagesreturns 404, which means GitHub Pages has never been provisioned for this repository.actions/configure-pagesaccepts anenablementparameter that asks the action to create the Pages site on first run; the workflow already grants thepages: writeandid-token: writepermissions it needs to do so.Fallback
If the org-level
GITHUB_TOKENrestrictions still prevent automatic provisioning, a repository admin only needs to flip Settings -> Pages -> Build and deployment -> Source toGitHub Actionsonce; subsequent deploys will then succeed without the failure.Validation
python -c "import yaml; yaml.safe_load(open(...))"actions/configure-pages@v5step