fix: prevent GitHub Pages deploy cancellation on concurrent workflow runs#150
Merged
Merged
Conversation
…tive deployments from being cancelled Agent-Logs-Url: https://github.com/DavidKRK/DavidKRK.github.io/sessions/20c8a8df-3239-4343-8a3c-b04e91465915 Co-authored-by: DavidKRK <136035295+DavidKRK@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
DavidKRK
April 4, 2026 05:55
View session
|
|
Contributor
There was a problem hiding this comment.
Pull request overview
Adjusts GitHub Actions workflow concurrency settings so GitHub Pages deployments are queued instead of being cancelled by newer workflow runs.
Changes:
- Updated the Pages deployment workflow concurrency to set
cancel-in-progress: falsefor thepagesconcurrency group.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
With
cancel-in-progress: true, any new push togh-pageswhile a deployment was in-flight would cancel the activedeploy-pagesjob mid-execution, surfacing as a failed check. The deploy job for commitc679ec7dwas cancelled after ~7 minutes of polling GitHub Pages deployment status with no response.Change
deploy.yml:concurrency.cancel-in-progress: true→falseDeployments now queue rather than cancel, which is the correct semantics for a Pages deploy — there's no benefit to aborting a deployment already submitted to the Pages infrastructure.