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

Add possibility to setup multibranch #122

Open
maciekstosio opened this issue Sep 27, 2024 · 2 comments · May be fixed by #147
Open

Add possibility to setup multibranch #122

maciekstosio opened this issue Sep 27, 2024 · 2 comments · May be fixed by #147
Labels
🔨 new feature Extending the project with new feature

Comments

@maciekstosio
Copy link
Collaborator

maciekstosio commented Sep 27, 2024

We want to allow a multi-branch setup - what I mean by that the user can select processes (feature branch, main, release), and for each process user can select workflows.
I imagine that at the beginning there will be select which processes we're adding (feature branch, main, release) - I assume we can be opinionated about the main branch naming and release strategy. Then our current selection is displayed for each process. Additionally, when we run the selected recipe we can show for which process it will be used.

@maciekstosio
Copy link
Collaborator Author

The description is my idea of how it could work, but I'm open to other options on how to resolve it from a UX perspective.

@km1chno km1chno added the 🔨 new feature Extending the project with new feature label Sep 30, 2024
@km1chno
Copy link
Contributor

km1chno commented Sep 30, 2024

I imagine the survey could look something like this:

Select processes you'd like to run in every pull request
(learn more about feature branch processes: /* link to docs */)
[ ] option a
[ ] option b

Select processes you'd like to run on main branch each time its head commit changes
(learn more about main branch processes: /* link to docs */)
[ ] option a
[ ] option b

Select processes you'd like to run on release branch each time new code is pushed to it
(learn more about release branch processes: /* link to docs */
[ ] option a
[ ] option b

@km1chno km1chno linked a pull request Dec 19, 2024 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔨 new feature Extending the project with new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants