Replies: 2 comments
|
💬 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. ⭐ |
|
Good news: your site is already back. Run #16 of pages build and deployment (commit What's left is run #14 ( gh run cancel 38590856210 -R pive110/calculadora-rollos --force
# or, via REST:
gh api -X POST repos/pive110/calculadora-rollos/actions/runs/38590856210/force-cancelIf that's refused as well, it's safe to ignore; you also can't delete it yet, since a run can only be deleted once it has completed or is older than two weeks. For the future: if a deployment hangs like this again, you don't need to change the publishing source — you can request a fresh build of the latest commit on the default branch with: gh api -X POST repos/pive110/calculadora-rollos/pages/buildsDocs: Force cancel a workflow run · Deleting a workflow run · Request a GitHub Pages build |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
ARC (Actions Runner Controller)
Discussion Details
Subject: GitHub Pages deployment stuck in queue and timing out
Hello GitHub Support,
I'm experiencing persistent GitHub Pages deployment issues with my repository:
https://github.com/pive110/calculadora-rollos
updating_pagesbefore failing with "Timeout reached, aborting!"I have already tried reconfiguring the Pages publishing source to trigger a new deployment, but the problem persists.
Could you please investigate the stuck deployment and help restore normal GitHub Pages publishing?
Thank you.
All reactions