Skip to content

Auto-enable Pages on first deploy #1445

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bmehta001 wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −0
Open

Auto-enable Pages on first deploy #1445

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/deploy-docs-pages.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,8 @@ jobs:
steps:
- name: Configure GitHub Pages
uses: actions/configure-pages@v5
with:
enablement: true
Copy link
Copy Markdown
Contributor

@lalitb lalitb May 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you sure this will work? As per the Github docs - this option requires a token other than GITHUB_TOKEN to be provided.

Copy link
Copy Markdown
Contributor Author

@bmehta001 bmehta001 May 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are correct — I misread the docs. actions/configure-pages requires administration:write (PAT or GitHub App) to provision the Pages site; with only GITHUB_TOKEN, enablement: true will still 403. So this two-line diff is effectively a no-op.

Two real paths:

  1. Close this PR and have an admin flip Settings → Pages → Source: GitHub Actions once. One-time, no secret to maintain, cleanest.
  2. Add a PAGES_DEPLOY_TOKEN repo secret with admin:write and pass it via with.token here.

I'd lean (1) unless we expect this workflow to be cloned to new repos. Which would you prefer? Happy to push (2) or close in favor of (1).


- name: Deploy to GitHub Pages
id: deployment
Expand Down
Loading