Skip to content

Use cancel-in-progress for GitHub Pages deployments to prevent unbounded growth#6

Draft
ironictoo with Copilot wants to merge 2 commits into
devfrom
copilot/discuss-deployment-practices
Draft

Use cancel-in-progress for GitHub Pages deployments to prevent unbounded growth#6
ironictoo with Copilot wants to merge 2 commits into
devfrom
copilot/discuss-deployment-practices

Conversation

Copilot AI commented Mar 18, 2026

Copy link
Copy Markdown
Contributor

Each push to main creates a new GitHub Pages deployment entry. With cancel-in-progress: false, concurrent pushes queue independently, causing the deployment list to grow indefinitely rather than reflecting only the current live state.

Change

  • Set cancel-in-progress: true in the docs.yml concurrency block so a newer push cancels any in-flight deployment instead of queuing behind it
# .github/workflows/docs.yml
concurrency:
  group: "pages"
  cancel-in-progress: true  # was: false

Cancelled runs still appear in history but are marked cancelled, keeping the set of active/successful deployments bounded to the latest state.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Co-authored-by: ironictoo <8886583+ironictoo@users.noreply.github.com>
Copilot AI changed the title [WIP] Discuss deployment frequency and standards Use cancel-in-progress for GitHub Pages deployments to prevent unbounded growth Mar 18, 2026
Copilot AI requested a review from ironictoo March 18, 2026 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants