-
Notifications
You must be signed in to change notification settings - Fork 993
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
Grouped PR for packages that are released simultaneously #317
Comments
Thanks for getting in touch. I'm keen to do something about this - it's next on my list. In particular, when there are updates that need to be done together I'd like to bundle them into a single PR. We already do that for Ruby and Java, and I don't see any reason why we shouldn't for JS when all of your Angular / React packages are updated in lock-step. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within seven days. Thank you for your contributions. |
We're regularly spammed by |
Duplicate of #1296 |
Temp re-opening so I can close as "dupe" rather than "resolved" for clarity while skimming issue links. |
Hi i have an interesting proposal, I have recently used dependabot for managing my dependencies and i have this some sort of problem in scoped packages like
@angular/*
packages having multiple PRs wherein they are all released at the same time.Hopefully you'll take time considering this since updating Angular with multiple PRs results in many queued CI tasks and too many PRs that needs to merged Although there have been an auto-merge setting but i prefer not to use it. It would be better if it can be configured per repo basis.
The text was updated successfully, but these errors were encountered: