Repository navigation
Group Dependabot's updates, and make it part of the setup guide - #5
Merged
Merged
Conversation
The branch ruleset only merges a pull request that is up to date with main, so with one Dependabot pull request per dependency every merge put every other open update behind, and each needed a rebase and a fresh CI run before it could follow. One group per ecosystem, matching "*", turns that into one round per ecosystem per update run, the change sigrix-io/gatehouse made first. The file says the price: a bump that breaks something holds back the rest of its group until it is fixed or ignored. Checked against the published Dependabot configuration schema (schemastore dependabot-2.0). The file is read from the default branch, so this takes effect once it merges. docs/new-repository.md now lists the group as part of the Dependabot setup every public repository gets. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DpQHLFQaQN2SXqGUz3zZso
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.
What this changes
.github/dependabot.yml: the GitHub Actions updates get one group matching"*", so one PR per run instead of one per action. Why: the branch ruleset only merges a PR that's up to date withmain, so with separate PRs every merge puts the rest behind, and each needs·@·d·ependabot r·ebaseand a fresh CI run. The file's comment gives that reason and the price: a breaking bump holds back the rest of its group until it's fixed or ignored.docs/new-repository.md: the Dependabot step now includes one group per ecosystem, so new public repositories start that way. Every other public repository gets the same change in its own PR today;sigrix-io/gatehousealready has it.CHANGELOG.mdline. Neither action changes, so callers have nothing to bump.Does a caller see it?
No: config and docs only.
Checked
The config validates against the published Dependabot schema (schemastore
dependabot-2.0.json).🤖 Generated with Claude Code
https://claude.ai/code/session_01DpQHLFQaQN2SXqGUz3zZso
Generated by Claude Code