The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Adapting existing branch structure to Stash branching model

Jan Swaelens
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 13, 2013

Hi,

We are looking to adapt the new stash branching model to optimize our branch layout/usage.
Today our branches are named as follows:

  • master
  • release_1
  • release_2
  • etc.

What is the best way to adapt the the stash branch model where the branch names would be:

  • release/release_1
  • release/release_2
  • etc.

Should we just clone each current release branch to a new branch using the new Stash 'create branch' feature and then remove the old branches?

thanks

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Adam
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 13, 2013
Hi Jan, This doesn't answer your question as written, but the prefixes for Stash's branches ar configurable. You can change the prefix to release_ and everything should work for you. Look in the repo settings.
Jan Swaelens
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 13, 2013

Ah, that's even better! Thanks!

TAGS
AUG Leaders

Atlassian Community Events