It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
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?
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreBitbucket 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 ...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.