You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I prefer "release on every PR", I'm unsure if that will work with all of the libraries we are dealing with and we'd likely need to be able to release subsets as needed.
We could have a pr-group config in the configuration file, so that release-plz opens 1 PR for each group of packages. Dependent packages, even if not specified in the configuration, should be included in the pr as well.
This is similar to the grouped update feature of dependabot.
The text was updated successfully, but these errors were encountered:
I guess you can define one group for each crate :)
Having one PR for each crate, seems like a use case that could be enabled by this feature. But release-plz automatically figures out the groups, instead having the user to specify them.
Motivations
From #1019 (comment)
Solution
We could have a
pr-group
config in the configuration file, so that release-plz opens 1 PR for each group of packages. Dependent packages, even if not specified in the configuration, should be included in the pr as well.This is similar to the grouped update feature of dependabot.
The text was updated successfully, but these errors were encountered: