fix(ci): group Dependabot updates into one PR per ecosystem#699
Merged
Conversation
Without a groups: block Dependabot opens ONE PR PER DEPENDENCY. Every one of those PRs re-fires every workflow in the repo, so a single estate-wide bump (e.g. actions/checkout 7.0.0 -> 7.0.1) fans out into N PRs x M workflow runs of notifications. This was a measurable amplifier of the notification storm. Grouping with patterns: ["*"] makes the same bump a single PR, matching the 223 estate repos that already do this. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
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
1 participant
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.
This repo's
dependabot.ymlhas nogroups:block, so Dependabot opens one PR per dependency.Each of those PRs re-fires every workflow in the repo. So one estate-wide bump — say
actions/checkout7.0.0 → 7.0.1 — fans out into N PRs × M workflow runs worth of notifications. Combined with workflows that fail, that is a large amplifier of the notification flood.Fix
Add
groups:withpatterns: ["*"], so the same bump arrives as a single PR:This matches the 223 estate repos that already group (exemplar:
aerie). 50 did not — this is one of them.Update frequency and ecosystems are unchanged; only the PR batching changes.
🤖 Generated with Claude Code