-
Notifications
You must be signed in to change notification settings - Fork 37
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
Support multiple projects in a single change #571
Comments
Hmm, that is a good point, I wonder if using a multi-select would be more appropriate for projects. I wonder if it should be part of the config to choose between multi-select and single select. |
Yep! It's tricky to decide if single vs multi-select should be configurable. My personal choice is to always enable multi-select, as I can't think of a clear use case for restricting that every change should only belong to one project (and if so, the users will pick only one, as a sane default behavior). |
Btw I'm available to implement this change |
Yea sure, that would be good. Let me know if you need any onboarding help. |
I can 😉 but I'll log a new ticket for my concerns after upgrading to 1.16 |
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
When the projects feature is configured,
changie new
only allows a single project per change.Describe alternatives you've considered
Asking users to repeat the same change for multiple projects
Additional context
This is very useful for monorepos with shared packages, in which a package change affects multiple projects
The text was updated successfully, but these errors were encountered: