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

chore: Group dependabot updates #3641

Merged
merged 1 commit into from
Mar 10, 2024
Merged

chore: Group dependabot updates #3641

merged 1 commit into from
Mar 10, 2024

Conversation

twpayne
Copy link
Owner

@twpayne twpayne commented Mar 10, 2024

Refs #3637, as suggested by @halostatue.

Not sure how to test this, except waiting for the next dependabot run. It should be harmless, though.

@twpayne twpayne requested a review from halostatue March 10, 2024 13:30
Co-authored-by: Austin Ziegler <[email protected]>
@halostatue halostatue force-pushed the group-dependabot-updates branch from b715eba to 6c78b33 Compare March 10, 2024 18:25
@halostatue
Copy link
Collaborator

Yeah. The Dependabot grouping documentation isn't ideal, but simply specifying patterns won't do what you want.

I’ve amended your commit to have four groups: go-dev, go-prod, actions, and python. I have restricted the grouping to only apply for patch and minor upgrades. That way, if mkdocs were to go from 9 to 10, it would not be grouped together.

@twpayne
Copy link
Owner Author

twpayne commented Mar 10, 2024

Awesome, thank you!

@twpayne twpayne merged commit 30fb22a into master Mar 10, 2024
21 checks passed
@twpayne twpayne deleted the group-dependabot-updates branch March 10, 2024 18:57
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants