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

Implement release braching strategy #17

Open
2 tasks done
philnewm opened this issue Sep 17, 2024 · 0 comments
Open
2 tasks done

Implement release braching strategy #17

philnewm opened this issue Sep 17, 2024 · 0 comments

Comments

@philnewm
Copy link
Collaborator

Is there an existing issue for this?

  • I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

Right now the repository is step up pretty simple and just merges new features to main right away.

In the long run this should be extended to include temporary (bugfix only) release branches.
This will allow furhter development of additional features while a release version gets prepared in it's own branch.

How would you imagine the implementation of the feature?

This should be ahndled through github workflows entirely with minimal user interaction.

So a dispatch trigger should create the temporary branch and block any kind of feature or enhancement PRs.
Only allow for bugfixes.
It should also block PRs which branched away from develop initially.

Are there any labels you wish to add?

  • I have added the relevant labels to the feature request.

Describe alternatives you've considered:

No release branches and keeping main <-> develop structure

Additional context:

No response

@philnewm philnewm added the feature Additional functionality which doesn't exist yet label Sep 17, 2024
@mkolar mkolar removed the feature Additional functionality which doesn't exist yet label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants