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
Update dependabot.yaml to support grouped updates #1750
Comments
I can take this. It's easy and I've set this up at the last couple of workplaces |
This is a new feature, so I don't know that you have set this up, but sure, have at it. It technically may not be released yet, but should be within the next 2 weeks if its not available yet. This frequently trips up dependabot PRs where you see fail the PR build because dependencies dont match across the various projects in the solution. |
Hmm. there is a method of grouping updates so that there's one PR for multiple updates. Are you referring to the other issue that had to do with dependency updates running at different times, from tests/ versus src/ folder? I believe issue #1715? This is the existing feature I'm thinking of: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#groups |
One PR is key so that ci builds for PR don't break, I think, but happy to be proven wrong. The only other solution would be to put all projects in the same folder, which is messy |
I think I'll ignore the "groups" feature and wait for the new feature like you mentioned @jzabroski. I think after the new feature is released we'll determine if the "groups" feature i linked is relevant |
Support for grouped update PRs that group across directories with same ecosystem
The text was updated successfully, but these errors were encountered: