Adapting existing branch structure to Stash branching model


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?


1 answer

1 accepted

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.

Ah, that's even better! Thanks!

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,763 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you