Provided checkout command may result in expected source branch being used
David Rahija
I'm working with the ClickUp BitBucket integration and have done the following:
Opened up the BitBucket Integration and clicked the button to Create Branch. At this point I used the auto-generated branch name, selected my repository and selected the source branch. In this case, the source branch selected is
master
.It appears that the branch was created and I was then given a command to checkout the branch:
git checkout -b "t/CU-86ayf9811"
On my local development environment I ran this command, but then got to thinking, the
-b
switch tells Git to create a new branch using the current checked out branch as the source. My local development environment wasn't on the master
branch, so the local branch I created was branched off a different branch than the branch created through ClickUp. This should be updated to fetch the branch and then check it out, otherwise, users may run into unexpected results when trying to merge their changes. A one line command could be
get fetch origin "t/CU-86ayf9811" && get checkout "t/CU-86ayf9811"
Log In