chore: always create a new release branch and delete all old ones during new release action #894
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this way we're already prepared for hot-fix creation
Mend Scan Summary: ❌Repository: open-component-model/ocm
|
|
Integration Tests for d314584 run with result: Success ✅! |
|
Integration Tests for d314584 run with result: Success ✅! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it
When we create a new release, then let's always be prepared for a potential hotfix and create the release branch.
On the other hand, this will create a lot of unused branches over the time, so the PR will delete all older release branches.
In case of serious situation, where we really need to fix older versions, we still have the tags in place and would need to create manually a patched old release.
Which issue(s) this PR fixes
releates open-component-model/ocm-project#240