Are you sure branch labs does not already exist (as in this thread)? You can’t have both a file, and a directory with the same name. You’re trying to get git to do basically this: % cd .git/refs/heads % ls -l total 0 -rw-rw-r– 1 jhe jhe 41 2009-11-14 23:51 labs -rw-rw-r– 1 jhe jhe … Read more
I was looking for the same thing, and I found this question. Thank you for asking it! However, I found that the answers I see here don’t seem to quite give the answer you asked for (or that I was looking for) — they seem to give the G commit, instead of the A commit. … Read more
The answer given by Otto is good, but all the created branches will have “origin/” as the start of the name. If you just want the last part (after the last /) to be your resulting branch names, use this: for remote in `git branch -r | grep -v /HEAD`; do git checkout –track $remote … Read more
TL;DR answer git branch -r | grep -v ‘\->’ | sed “s,\x1B\[[0-9;]*[a-zA-Z],,g” | while read remote; do git branch –track “${remote#origin/}” “$remote”; done git fetch –all git pull –all (It seems that pull fetches all branches from all remotes, but I always fetch first just to be sure.) Run the first command only if there … Read more
There is a new feature (since V1.7.2) which makes this task a little more high-level than what’s in any of the other answers. git checkout now supports the –orphan option. From the man page: git checkout [-q] [-f] [-m] –orphan <new_branch> [<start_point>] Create a new orphan branch, named <new_branch>, started from <start_point> and switch to … Read more
You can control the default behavior by setting push.default in your git config. From the git-config(1) documentation: push.default Defines the action git push should take if no refspec is given on the command line, no refspec is configured in the remote, and no refspec is implied by any of the options given on the command … Read more
In general term, the main purpose of branching (a VCS – Version Control System – feature) is to achieve code isolation. You have at least one branch, which can be enough for sequential development, and is used for many tasks being recording (committed) on that same unique branch. But that model shows quickly its limit: … Read more
Yes, you should be able to do git reflog –no-abbrev and find the SHA1 for the commit at the tip of your deleted branch, then just git checkout [sha]. And once you’re at that commit, you can just git checkout -b [branchname] to recreate the branch from there. Credit to @Cascabel for this condensed/one-liner version … Read more
Assuming that the remote repository has a copy of the develop branch (your initial description describes it in a local repository, but it sounds like it also exists in the remote), you should be able to achieve what I think you want, but the approach is a bit different from what you have envisioned. Git’s … Read more
Note: the git1.7.10 (April 2012) actually allows you to clone only one branch: # clone only the remote primary HEAD (default: origin/master) git clone <url> –single-branch # as in: git clone <url> –branch <branch> –single-branch [<folder>] (<url> is the URL if the remote repository, and does not reference itself the branch cloned) You can see … Read more