Cloning a repository across Stash instances

Hi, my organization is using Stash to manage Git repositories. Due to some re-structuring, we need to move one git repository to another Stash instance altogether. Both the instances are up and running, and people in my organization are using them for their day-to-day work.

How should I go ahead with this cloning/migration?

I got to know that Closed pull request history will be lost during such cloning. Is this true? Is there any other data which would be lost during this cloning?

1 answer

1 accepted

git cloning will only get all the git repository information and it will not get Stash related features like Pull Requests. 

One of your approach here is to copy the server side stuff (like the Stash Database information) and load it in your new Stash instance. We are doing this approach when we like to copy our Stash prod instance to Stash test instance.

Thank you very much smile

 

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,769 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