For the vast majority[1] of visitors here, the correct and simplest answer to the question “How do I list all remote branches in Git 1.7+?” is: git branch -r For a small minority[1] git branch -r does not work. If git branch -r does not work try: git ls-remote –heads <remote-name> If git branch -r … Read more
Submodules are always checked out in a detached HEAD mode. That is because a submodule will checkout the SHA1 stored in the special entry in the index of the parent repo. Plus, if you want a submodule to follow the branch you have registered in the .gitmodules, you need: git submodule update –init –remote The … Read more
You might benefit from the workflow Scott Chacon describes in Pro Git. In this workflow, you have two branches that always exist, master and develop. master represents the most stable version of your project and you only ever deploy to production from this branch. develop contains changes that are in progress and may not necessarily … Read more
git remote prune origin will remove all such stale branches. That’s probably what you’d want in most cases, but if you want to just remove that particular remote-tracking branch, you should do: git branch -d -r origin/coolbranch (The -r is easy to forget…) -r in this case will “List or delete (if used with -d) … Read more
Update: Using Git Switch All of the information written below was accurate, but a new command, git switch has been added that simplifies the effort. If daves_branch exists on the remote repository, but not on your local branch, you can simply type: git switch daves_branch Since you do not have the branch locally, this will … Read more
List remote Git branches by author sorted by committer date: git for-each-ref –format=”%(committerdate) %09 %(authorname) %09 %(refname)” –sort=committerdate
git checkout -b BRANCH_NAME creates a new branch and checks out the new branch while git branch BRANCH_NAME creates a new branch but leaves you on the same branch. In other words git checkout -b BRANCH_NAME does the following for you. git branch BRANCH_NAME # create a new branch git switch BRANCH_NAME # then switch … Read more
When I search for ‘git check if branch exists’ on a search engine, this page is the first one I see. I get what I want, but I’d like to provide a updated answer since the original post was from 2011. git rev-parse –verify <branch_name> This is essentially the same as the accepted answer, but … Read more
How do we merge the master branch into the feature branch? Easy: git checkout feature1 git merge master There is no point in forcing a fast forward merge here, as it cannot be done. You committed both into the feature branch and the master branch. Fast forward is impossible now. Have a look at GitFlow. … Read more
You can create a branch as an orphan: git checkout –orphan <branchname> This will create a new branch with no parents. Then, you can clear the working directory with: git rm –cached -r . and add the documentation files, commit them and push them up to github. A pull or fetch will always update the … Read more