Skip to content

chore(ci): migrate website deploy to actions/deploy-pages#64

Merged
kirkone merged 1 commit into
mainfrom
chore/deploy-website-pages-action
May 3, 2026
Merged

chore(ci): migrate website deploy to actions/deploy-pages#64
kirkone merged 1 commit into
mainfrom
chore/deploy-website-pages-action

Conversation

@kirkone
Copy link
Copy Markdown
Contributor

@kirkone kirkone commented May 3, 2026

Replaces the cross-repo git push to Spectara/Revela.Website with a native GitHub Pages deployment via actions/upload-pages-artifact + actions/deploy-pages.

Benefits

  • No PAT — OIDC authentication instead of WEBSITE_DEPLOY_TOKEN
  • Native Pages deployment history — one-click rollback in the Pages UI
  • Single-repo setupSpectara/Revela.Website becomes obsolete (will be archived)
  • Fewer moving parts — no manual git config, no manual force-push

Pre-requisites (already done)

  • Pages source for Spectara/Revela.Website set to "None" (custom domain freed)
  • Pages source for Spectara/Revela set to "GitHub Actions"
  • Custom domain revela.website claimed
  • Enforce HTTPS active

Safety

  • A verify step fails the workflow if CNAME or .nojekyll ever go missing from the build output (would otherwise drop the custom domain)
  • Concurrency group renamed to pages (Pages backend convention) with cancel-in-progress: false to avoid cancelling in-flight deploys

Cleanup after merge

  • Delete WEBSITE_DEPLOY_TOKEN secret
  • Archive Spectara/Revela.Website repo

Replaces the cross-repo git push to Spectara/Revela.Website with a native GitHub Pages deployment via actions/upload-pages-artifact + actions/deploy-pages.

Benefits: no PAT needed (OIDC instead), Pages-native deployment history with one-click rollback, single-repo setup, fewer moving parts.

Pages source for Spectara/Revela must be set to 'GitHub Actions' with custom domain revela.website (already done). The _static/CNAME and _static/.nojekyll files in the website source survive every build; a verify step fails the workflow if they ever go missing.

Concurrency group renamed to 'pages' (Pages backend convention) with cancel-in-progress=false to avoid cancelling in-flight deploys.
@kirkone kirkone merged commit f9ce675 into main May 3, 2026
3 checks passed
@kirkone kirkone deleted the chore/deploy-website-pages-action branch May 3, 2026 14:48
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.

1 participant