ci: stop dependabot from triggering heavy workflows - #2
Merged
Merged
Conversation
- Add a top-level concurrency group to Test Features and Validate Features so a new push to a PR supersedes its in-flight run; pushes to main are never cancelled. - Cap dependabot's github-actions updates at 3 open pull requests. - Publish Features is left untouched: it is a publish workflow and is unsafe to cancel mid-run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015eDrUXwb4BZWXUuwpNMkDn
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
2 participants
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.
Part of the ecosystem-wide effort to cut wasted CI minutes (same change as AgentsKit-io/agentskit#1579).
What changed
.github/workflows/test.yaml— added a top-levelconcurrency:group so a new push to a PR supersedes the in-flight run.cancel-in-progressis gated ongithub.event_name == 'pull_request', so pushes tomainalways run to completion..github/workflows/validate.yml— same top-levelconcurrency:group, same guard..github/dependabot.yml— addedopen-pull-requests-limit: 3to thegithub-actionsentry, which had no limit (defaulting to 5).What deliberately did not change
.github/workflows/release.yaml(Publish Features) — a publish workflow; cancelling one mid-run is unsafe, so no concurrency group was added. It isworkflow_dispatch-only anyway.github.actor != 'dependabot[bot]'. This repo's three jobs (package,playbook,scenarios) are its package/test jobs, not auxiliary heavy jobs — and since the only dependabot ecosystem here isgithub-actions, those tests are exactly what validates an action bump. Skipping them would leave dependabot PRs unverified.Verification
Each edited file was re-parsed with
python3 -c "import yaml; yaml.safe_load(...)". No files outside.github/were touched.🤖 Generated with Claude Code
https://claude.ai/code/session_015eDrUXwb4BZWXUuwpNMkDn
Generated by Claude Code