I'm evaluating Stash and SourceTree for my organization. We use gitflow today, and are simply using command line interface. We want to add code review, and the Stash pull request feature looks like it would fit the bill very nicely.
I believe I've figured out how to work within SourceTree and Stash up to the point where we create a pull request. At that point I've merged the change into develop on Stash and it properly deletes the branch on the Stash repo.
However, I'm left with a feature branch on the local repository. What should we do with that feature branch? Finishing it on the local repository results in a merge to develop. But, the code's already been merged to develop in the Stash repo. Seems like I get duplicated merges.
Or, should we simply delete the local branch after it's been merged into develop in the Stash repo?
It's as simple as deleting the local branch. :)
If you find that the 'remote' feature branch still hangs around in your local repository, even though Stash deleted it, you might want to 'prune' during fetch.
The Stash team uses Pull Requests as our primary source of code review without any problems. Let us know if you find something missing.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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 ...
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!
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