ci: migrate website deployment to GitHub Actions - #2505
Merged
Brendan Walsh (BrendanWalsh) merged 4 commits intoFeb 14, 2026
Conversation
Phase 1 of website deployment migration from ADO to GitHub Actions. Builds the website on pushes to master (when docs/website/docgen change) and uploads the result as an artifact for validation. Does NOT deploy to GitHub Pages yet — just validates the build pipeline works correctly on GH Actions before switching over.
|
Hey Brendan Walsh (@BrendanWalsh) 👋! We use semantic commit messages to streamline the release process. Examples of commit messages with semantic prefixes:
To test your commit locally, please follow our guild on building from source. |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
- On PRs: build only, upload artifact for preview - On master push: build + deploy to GitHub Pages - Replaces broken ADO WebsiteAutoDeployment (SAML SSO 403) - Uses GITHUB_TOKEN (no PATs, no SAML issues) - Requires Pages source set to 'GitHub Actions' in repo settings
Brendan Walsh (BrendanWalsh)
force-pushed
the
brwals/website-deploy-preview
branch
from
February 14, 2026 08:01
8be750b to
95e8623
Compare
Brendan Walsh (BrendanWalsh)
deleted the
brwals/website-deploy-preview
branch
February 14, 2026 08:17
3 tasks
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.
Related Issues/PRs
Website deployment via ADO (
WebsiteAutoDeploymentjob) fails with SAML SSO 403 errors ongit push --force origin gh-pages. The PAT inmmlspark-keysKey Vault has lost SAML SSO authorization. This causes CI builds to show as failed even when all real tests pass.What changes were made?
Migrates website deployment from ADO to GitHub Actions using
actions/deploy-pages.Added:
.github/workflows/website-deploy.ymlactions/deploy-pagesdocs/,website/, ortools/docgen/changeGITHUB_TOKEN— no PATs, no SAML SSO issuesconcurrencygroups cancel superseded buildsworkflow_dispatchsupport for manual deploysRemoved from
pipeline.yamlWebsiteAutoDeploymentjob (broken, 100% failure rate on CI builds)websiteAutoDeployparameter (no longer needed)Validated output
Compared the GH Actions build output against the current live site (
gh-pagesbranch):.nojekyllfile (not needed for Actions deploys)Post-merge step
Change Pages source to GitHub Actions:
The
gh-pagesbranch remains as rollback if needed.How is this tested?
Does this PR introduce a breaking change?
No. Website deployment won't activate until the Pages source setting is changed post-merge.