Repository navigation
Don't group by dependency name - #683
Merged
Merged
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
The single-line removal matches the stated intent, preserves the remaining configuration, and has no identified blocking issues.
No open issues 🎉
What changed in this PR
This PR simplifies Dependabot’s NuGet grouping configuration by removing dependency-name grouping, addressing the grouping concern linked from PR #682.
Changes:
- Removes
group-by: dependency-namewhile retaining thenugetgroup and its wildcard pattern. - Leaves other update settings unchanged.
| File | Description |
|---|---|
.github/dependabot.yml |
Removes dependency-name grouping from the NuGet update group. |
Review effort: Balanced
gewarren
enabled auto-merge (squash)
October 24, 2026 00:29
guardrex
approved these changes
Oct 24, 2026
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.
See #682 (comment).