Open mirrom opened 9 years ago
I guess my ticket is closely related to #109.
The --track, or -t, flag was the recommended solution as per the following sources:
As a convenience, --track without -b implies branch creation
If no -b option is given, the name of the new branch will be derived from the remote-tracking branch https://git-scm.com/docs/git-checkout
So, the basic command for checking out a remote branch and setting up tracking seems to be:
git checkout --track remote/branch
For me the checkout of a remote branch does not work as intended. As you can see on the screenshot my remote branches are shown with a leading
origin/
:If I click on a remote branch it gets checked out with the leading
origin/
as you can see with the local branchesorigin/master
andorigin/features/T170-split-files
. Actually it checks out a new branch based on the current working branch:I checked out the local branches
master
,develop
andfeatures/T170-split-files
from the command line by:The local branches
features/T170-split-files
andorigin/features/T170-split-files
clearly differ as the latter is based on themaster
branch. Furthermore if I would push the latter branch with the suggested$ git push --set-upstream origin origin/features/T170-split-files
, it would create the remote branchorigin/origin/features/T170-split-files
which I could checkout as local branchorigin/origin/features/T170-split-files
and so on and so on..Is there a way that git-remote can handle the leading
origin/
?