Migrate GitHub Pages to modern Actions-based deployment#321
Open
rgregg-msft wants to merge 1 commit intomasterfrom
Open
Migrate GitHub Pages to modern Actions-based deployment#321rgregg-msft wants to merge 1 commit intomasterfrom
rgregg-msft wants to merge 1 commit intomasterfrom
Conversation
Replace classic branch-based publishing with a GitHub Actions workflow using configure-pages, jekyll-build-pages, upload-pages-artifact, and deploy-pages. Also moves CNAME into the docs/ source directory. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
Author
Post-merge action requiredAfter this PR is merged, go to Settings → Pages and change the source from "Deploy from a branch" to "GitHub Actions". This is the final step to complete the migration — the new workflow won't be used until that setting is switched. |
Contributor
There was a problem hiding this comment.
Pull request overview
Migrates the repository’s GitHub Pages publishing from the legacy “deploy from branch” model to the modern GitHub Actions–based Pages deployment pipeline, while ensuring the custom domain is included in the built site output.
Changes:
- Added a GitHub Actions workflow to build the site from
./docsusing the official Pages action stack and deploy it to GitHub Pages. - Added
docs/CNAMEso the custom domain (apidoctor.md) is preserved as part of the Pages build output.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
docs/CNAME |
Adds custom domain configuration into the Pages source directory so it’s emitted into the deployed artifact. |
.github/workflows/pages.yml |
Introduces an Actions-based build + deploy workflow using configure-pages → jekyll-build-pages → upload-pages-artifact → deploy-pages. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -0,0 +1 @@ | |||
| apidoctor.md No newline at end of file | |||
| destination: ./_site | ||
|
|
||
| - name: Upload artifact | ||
| uses: actions/upload-pages-artifact@v3 |
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
configure-pages→jekyll-build-pages→upload-pages-artifact→deploy-pagesaction stackCNAMEinto thedocs/source directory so the custom domain (apidoctor.md) is preserved in the built sitePost-merge manual step
In the repo Settings → Pages, change the source from "Deploy from a branch" to "GitHub Actions" to complete the migration.
Test plan
Deploy GitHub Pagesworkflow triggers and completes successfully🤖 Generated with Claude Code