Since the branches RELEASE and DEVELOP are automatically protected and recognized as persistent and protected it would be nice that when the popup for “Create merge session” has the reciprocal merge as the default option (while still being able to chose to archive the branch). RELEASE and DEVELOP won’t be likely to be archived afterwards.
It’ll prevent that you accidentally archive such a branch and it save a few clicks.
+23When both branches are protected, reciprocal merging is the only option.
When the source branch is unprotected, the default behavior is to archive the branch as it is a branch that does not have an indefinite lifespan. Unprotected branches are mostly Feature branches, Hotfix branches, or Test branches that will be discarded later. The happy flow is to merge the feature into the protected branch and thereafter archive the feature branch.
+2
+9As mentioned in this release note, during the upgrade to 2024.1 we automatically marked branches named MAIN, RELEASE, and DEVELOP as protected, based on their name. At the moment I cannot say why this was not done for your DEVELOP branch, unless it was created after the upgrade to the 2024.1.
Although we could figure this out (which would require a ticket with reproduction in the form of a database backup before the 2024.1 upgrade), I think it would be more effective in this situation if you activate the checkbox yourself in this case.
In your opinion, did our responses cover all parts of your idea?
+9+9Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
