docs: document transient GitHub Pages 503 deployment failure (no code fix needed) - #10
Merged
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job deploy
docs: document transient GitHub Pages 503 deployment failure (no code fix needed)
Aug 17, 2026
benrushscience
marked this pull request as ready for review
August 17, 2026 16:53
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.
The "deploy" job in the
pages build and deploymentworkflow failed with HTTP 503 — a transient GitHub Pages infrastructure outage, not a code regression.Root Cause
The artifact was built and uploaded successfully. The failure occurred only at the final deployment API call:
GitHub's Pages deployment API was temporarily unavailable at
2026-08-17T15:05:17Z. This is a server-side issue on GitHub's infrastructure, unrelated to repository content or workflow configuration.Resolution
No code changes required. The deployment will succeed on the next push to
mainthat re-triggers the built-in Pages workflow.