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. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Actions Runner
Discussion Details
Repository: LPI-LLC/lighthouse-inspections
Workflow: pages build and deployment #97
My GitHub Pages deployment has remained queued for an extended period and cannot be cancelled. Several previous Pages deployments were cancelled because a higher-priority deployment was waiting.
The build previously completed successfully, but the deploy job was cancelled. When I attempted to cancel workflow #97, GitHub displayed “Failed to cancel workflow.” I also reran the workflow, but the rerun remains queued.
The last successful Pages deployment was workflow #90. All later commits are saved on the main branch but have not been published.
Please advise how I can release the stuck Pages deployment/concurrency lock and publish the current main branch.



Beta Was this translation helpful? Give feedback.
All reactions