Skip to main content
Solved

Creating a new RELEASE branch

  • April 2, 2024
  • 1 reply
  • 59 views

Dave Bieleveld Starcode
Vanguard
Forum|alt.badge.img+2

So we want to implement branches as described in this article:

Manage branches with Thinkwise | Thinkwise Community (thinkwisesoftware.com)

And the automatically protected branch names:

https://docs.thinkwisesoftware.com/docs/sf/overview#:~:text=corresponding%20runtime%20configuration.-,Protect%20a%20branch%E2%80%8B,remove%20protection%20as%20needed.,-You%20can%20recognize

In our current situation, we have feature branches with origin DEVELOP, with origin MAIN. How can we create a branch RELEASE between DEVELOP and MAIN?

Let’s say we roll-up all our branches back to the main and archive them.  Then we can create a RELEASE branch from the main, but then we can’t create a branch named DEVELOP from the release branch, since there is already a archived branch DEVELOP. And we can’t rename it either.

Some advice?

Best answer by Mark Jongeling

Hi Dave,

Current way to do this is to merge Develop to MAIN, make Develop not protected and delete it. Thereafter create the desired branch structure from starting MAIN. For example: MAIN > RELEASE > DEVELOP (This branch will actually still contain old history data because history data is not cleaned after deleting a branch)

(Renaming model and branches is currently not possible due to all underlying history tables)

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

1 reply

Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Administrator
  • 3927 replies
  • Answer
  • April 2, 2024

Hi Dave,

Current way to do this is to merge Develop to MAIN, make Develop not protected and delete it. Thereafter create the desired branch structure from starting MAIN. For example: MAIN > RELEASE > DEVELOP (This branch will actually still contain old history data because history data is not cleaned after deleting a branch)

(Renaming model and branches is currently not possible due to all underlying history tables)


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings