-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Option to group all updates into a single PR for a repo #2203
Comments
Ack, was about to point you to deppbot but can see they've now shut down. Grouping everything together was exactly their service. Grouping is still high up on our list but we're a tiny team. We'll get to it :-) |
I'd love to see this feature. The way I see it, is that I like the "purity" of of being able to isolate which dependency caused a build failure or suspect deploy, but realistically:
|
This is a feature that is part of the Depfu bot service but unlike Dependabot they do not integrate as well (i.e. with security alerts) nor update Github based dependencies and have a tendency to not update |
@feelepxyz Any thoughts on this? |
@rebelagentm would be ace and high up on the list of features to prioritise once we have some spare capacity as a team. Sadly at least another six months out 😢 It's quite a significant project and depends on https://github.com/dependabot/feedback/issues/5 |
Duplicate of #1190 |
This is similar to dependabot/feedback#5, but would be an option to raise a single PR (or update a PR if there is one open already) whenever there are updates available for a repo. Making this tradeoff for a repo would have the advantage of having fewer PRs to deal with, so less time dealing with dependency updates - particularly if you manage a lot of repos.
The text was updated successfully, but these errors were encountered: