Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make dependabot grouping work on all update types #166

Merged
merged 1 commit into from
Feb 6, 2024

Conversation

kdarkhan
Copy link
Collaborator

The initial version defined groups only for cargo
deps. Because of that, we have 2 separate PRs related to github-actions. This ensures that grouping logic works for all deps.

Copy link
Collaborator

@mgeisler mgeisler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me approve this now — then you can fix the comment about groups if you also agree with my reasoning.

patch:
update-types:
- patch
groups:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure you can use groups as a top-level item like this. My impression was that it has to be nested under an item in updates. See how groups is mentioned under updates here: Configuration options for the dependabot.yml file.

In Comprehensive Rust, I simply duplicated the groups for each type of update.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. I based my approach on the example 1 in the official doc s but it might be just not a full example. I just amended the approach and duplicated the definitions.

The initial version defined groups only for cargo
deps. Because of that, we have 2 separate PRs related
to `github-actions`. This ensures that grouping logic
works for all deps.
@kdarkhan kdarkhan merged commit 7e3e5c6 into google:main Feb 6, 2024
7 checks passed
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