Skip to content
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

Closed
fsmaia opened this issue Oct 31, 2023 · 5 comments · Fixed by #579
Closed

Support multiple projects in a single change #571

fsmaia opened this issue Oct 31, 2023 · 5 comments · Fixed by #579
Assignees
Labels
enhancement New feature or request

Comments

@fsmaia
Copy link

fsmaia commented Oct 31, 2023

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

@fsmaia fsmaia added the enhancement New feature or request label Oct 31, 2023
@miniscruff
Copy link
Owner

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.

@fsmaia
Copy link
Author

fsmaia commented Nov 2, 2023

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).

@fsmaia
Copy link
Author

fsmaia commented Nov 2, 2023

Btw I'm available to implement this change

@miniscruff
Copy link
Owner

Yea sure, that would be good. Let me know if you need any onboarding help.

@TheSpyder
Copy link
Contributor

I can't think of a clear use case for restricting that every change should only belong to one project

I can 😉 but I'll log a new ticket for my concerns after upgrading to 1.16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
3 participants