New to bitbucket/Jira integrations, using VSCode + Powershell, on Windows & Docker.
I'm familiar with when I don't have an existing branch, I need to pass the '-b' flag to force that branch to be created locally. However, I'm noticing when I create my branch inside the Jira interface (which is integrated w/ my Bitbucket repo), it's leaving that flag off. (See attached image) & note the missing '-b' flag where it offers up the prepared copy/paste commands.
Referencing Git documentation, this command as displayed below will simply switch, not ALSO create. If the branch doesn't exist it can't switch & doesn't auto create. I can obviously manage this manually, but shouldn't any 1st time story be using the '-b' flag by default, is this something I can configure on my end & haven't found documentation on?
Hello @Joe Rajewski ,
I have moved this question to the Bitbucket section since when you click on the "Create New Branch" link in the Jira issue view this is actually redirecting to:
Once this has been said, please notice that the branch has already been created when the dialog you pasted the screenshot of is displayed.
Hi @Joe Rajewski ,
I might not be the best person to answer this question (I only got it since it was in the Jira section) however, from what I can read in the Bitbucket documentation for git checkout, in modern versions of Git you don't need to create a new branch, you can checkout the remote one like it was local:
Git Checkout a Remote Branch
When collaborating with a team it is common to utilize remote repositories. These repositories may be hosted and shared or they may be another colleague's local copy. Each remote repository will contain its own set of branches. In order to checkout a remote branch you have to first fetch the contents of the branch.
git fetch --all
In modern versions of Git, you can then checkout the remote branch like a local branch.
Older versions of Git require the creation of a new branch based on the
In other words, in modern versions of Git you don't need to use the -b flag. I have tested this locally in order to confirm, and it works as documented:
$ git fetch && git checkout TSP-23-one-more
* [new branch] TSP-23-one-more -> origin/TSP-23-one-more
Branch 'TSP-23-one-more' set up to track remote branch 'TSP-23-one-more' from 'origin'.
Switched to a new branch 'TSP-23-one-more'
Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster ! While we’re all excited about the new improvements to Bitbucket ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events