GitHub Pages deployment times out after repository rename (build succeeds) #212096
Unanswered
jadexuan155229-dot
asked this question in
Actions
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Workflow Deployment
Discussion Details
Hello GitHub Support,
I am experiencing a persistent GitHub Pages deployment failure after renaming my repository.
Repository:
https://github.com/jadexuan155229-dot/eight-thousand-miles-away-wiki
Previous repository name:
cangyun-wikiNew Pages URL:
https://jadexuan155229-dot.github.io/eight-thousand-miles-away-wiki/
Affected commit:
e299379Issue description
On 4 November 2026, I renamed my repository from
cangyun-wikitoeight-thousand-miles-away-wikiand updated the Vite base path, package metadata, website URLs, and deployment-related references.Before the rename, GitHub Pages deployments completed successfully, usually within approximately 30 seconds.
Since the rename, every deployment attempt has failed during the
actions/deploy-pages@v4step.The build job consistently succeeds, including installation, Vite compilation, Pages configuration, and artifact upload. The deployment job successfully creates a Pages deployment but then repeatedly polls for its status without receiving a successful response.
After approximately 10 minutes, the job fails with:
Some attempts remain in
updating_pages, while subsequent attempts return an empty status.Steps already attempted
main.All attempts produced the same timeout.
Relevant workflow runs
The new Pages URL has also served outdated HTML referencing assets that return 404 errors.
Request
Could you please investigate whether the repository rename has left the GitHub Pages site or deployment environment in an inconsistent state, or whether there is an issue with the Pages publishing backend?
I would appreciate guidance on restoring successful deployments without recreating the repository or losing its history.
Thank you for your assistance.
All reactions