If I have an n number of commits, how can I create a branch from the n-3 commit?
23 Answers
Create the branch using a commit hash:
git branch branch_name <commit-hash>
Or by using a symbolic reference:
git branch branch_name HEAD~3
To checkout the branch while creating it, use:
git checkout -b branch_name <commit-hash or HEAD~3>
8 Comments
git push origin BRANCH_NAME<sha1-of-commit> run git checkout -b <name-of-branch> <sha1-of-commit> but if the branch already exists git checkout -B <name-of-branch> <sha1-of-commit>switch command using the create option: git switch -c branchname <sha1-of-commit or HEAD~3>To do this on github.com:
- Go to your project.
- Click on the "Commits".
- Click on the <> ("Browse the repository at this point in the history") on the commit you want to branch from.
- Click on the "tree: xxxxxx" up in the upper left. Just below the language statistics bar, you'll get the option to "Find or Create Branch" (just type in a new branch name there)

The magic can be done by git reset.
Create a new branch and switch to it (so all of your latest commits are stored here)
git checkout -b your_new_branchSwitch back to your previous working branch (assume it's master)
git checkout masterRemove the latest x commits, keep master clean
git reset --hard HEAD~x # in your case, x = 3
From this moment on, all the latest x commits are only in the new branch, not in your previous working branch (master) any more.
14 Comments
git reset --hard is not a good idea if you already have pushed the commit to origin...git push --force if you had already pushed the branch beforeIf you are not sure which commit you want to branch from in advance you can check commits out and examine their code (see source, compile, test) by
git checkout <sha1-of-commit>
once you find the commit you want to branch from you can do that from within the commit (i.e. without going back to the master first) just by creating a branch in the usual way:
git checkout -b <branch_name>
8 Comments
git checkout -b and git branch seem to always checkout the head for me, not the current detached position, unless the hash is specified as an extra argument. see git switch -c newbranchnamebranch or checkout -b command, not just the <branch_name>. The first command you show is actually irrelevant if you already knew the hash.Simply run:
git checkout -b branch-name <commit>
For example:
git checkout -b import/january-2019 1d0fa4fa9ea961182114b63976482e634a8067b8
The checkout command with the parameter -b will create a new branch and it will switch you over to it.
2 Comments
git fetch & git branch command on your project's folder using the terminal, then check if the feature branch exists, if this is case then yes, of course you wont be able to create a branch from deleted branches, you could also revert a branch deletion in case the branch is gonegit checkout -b <branch-name> <sha1-of-commit>
3 Comments
git branch branchname <sha1-of-commit>" (from the accepted answer)?git checkout -b to create a new branch.This creates the branch with one command:
git push origin <sha1-of-commit>:refs/heads/<branch-name>
I prefer this way better than the ones published above, because it creates the branch immediately (does not require an extra push command afterwards).
1 Comment
A great related question is: How the heck do you figure this out using the --help option of Git? Let's try this:
git branch --help
We see this output:
NAME
git-branch - List, create, or delete branches
SYNOPSIS
git branch [--color[=<when>] | --no-color] [-r | -a]
[--list] [-v [--abbrev=<length> | --no-abbrev]]
[--column[=<options>] | --no-column]
[(--merged | --no-merged | --contains) [<commit>]] [--sort=<key>]
[--points-at <object>] [<pattern>...]
git branch [--set-upstream | --track | --no-track] [-l] [-f] <branchname> [<start-point>]
git branch (--set-upstream-to=<upstream> | -u <upstream>) [<branchname>]
git branch --unset-upstream [<branchname>]
git branch (-m | -M) [<oldbranch>] <newbranch>
git branch (-d | -D) [-r] <branchname>...
git branch --edit-description [<branchname>]
Gobbledegook.
Search through the subsequent text for the word "commit". We find this:
<start-point>
The new branch head will point to this commit. It may be given as a branch name, a
commit-id, or a tag. If this option is omitted, the current HEAD will be used instead.
We're getting somewhere!
Now, focus on this line of the gobbledegook:
git branch [--set-upstream | --track | --no-track] [-l] [-f] <branchname> [<start-point>]
Condense that to this:
git branch <branchname> [<start-point>]
And done.
Comments
Using Sourcetree | The easiest way.
- First, checkout the branch that you want to take the specific commit to make a new branch.
- Then look at the toolbar, select Repository > Branch ... the shortcut is Command + Shift + B.
- And select the specific commit you want to take. And give a new branch name then create a branch!
Comments
This is what I did:
C:\Users\[path]\build>git checkout -b responsivenavigation 8a75b001096536b3216022484af3026aa9c7bb5b
Switched to a new branch 'responsivenavigation'
C:\Users\jaimemontoya\[path]\app>git branch
master
* responsivenavigation
In this case, 8a75b001096536b3216022484af3026aa9c7bb5b was and old commit belonging to the master branch.
Comments
No one mentioned git switch yet?
You can do:
git checkout <commit-hash>
Or by using a symbolic reference:
git checkout HEAD~3
And then:
git switch -c my-new-feature-branch
2 Comments
git checkout -b and git branch seem to always checkout the head for me, not the current detached position.A quick way to do it on your GitHub repository would be as followed:
3 Comments
Go to a particular commit of a Git repository
Sometimes when working on a Git repository you want to go back to a specific commit (revision) to have a snapshot of your project at a specific time. To do that all you need it the SHA-1 hash of the commit which you can easily find checking the log with the command:
git log --abbrev-commit --pretty=oneline
which will give you a compact list of all the commits and the short version of the SHA-1 hash.
Now that you know the hash of the commit you want to go to you can use one of the following two commands:
git checkout HASH
or
git reset --hard HASH
checkout
git checkout <commit> <paths>
Tells git to replace the current state of paths with their state in the given commit. Paths can be files or directories.
If no branch is given, Git assumes the HEAD commit.
git checkout <path> // Restores <path> from your last commit. It is a 'filesystem-undo'.
If no path is given, Git moves HEAD to the given commit (thereby changing the commit you're sitting and working on).
git checkout branch // Means switching branches.
reset
git reset <commit> // Resets the current pointer to the given commit.
If you are on a branch (you should usually be), HEAD and this branch are moved to commit.
If you are in detached HEAD state, Git reset does only move HEAD. To reset a branch, first check it out.
If you wanted to know more about the difference between git reset and Git checkout I would recommend to read the official Git blog.
1 Comment
git log --abbrev-commit --pretty=oneline can be abbreviated to git log --onelineTo do this in Eclipse:
- Go to "Git Repository Exploring" Perspective.
- Expand "Tags" and choose the commit from which you want to create branch.
- Right click on the commit and choose "Create Branch".
- Provide a branch name.
It will create a local branch for you. Then whenever you push your changes, your branch will be pushed to the remote server.
Comments
For Git GUI users you can visualize all the history (if necessary) and then right click on the commit you wish to branch from and enter the branch name.
2 Comments
You can do it in Stash.
- Click the commit
- On the right top of the screen click "Tag this commit"
- Then you can create the new branch from the tag you just created.
2 Comments
I was able to do it like so:
git branch new_branch_name `git log -n 1 --skip 3 --format=%H`
Where you must enter the skip value. 0 is the latest, 1 is the previous, 2 is the commit before that, etc.
2 Comments
HEAD~1 (where 1 specifies 1 commit back)?With Sourcetree (version currently used: 3.1.3)
Open the History in Sourcetree
It will list all the commits in the main window
Right-click on the desired commit and click on the
Branch...option.Give a name for the branch in the new window and click
Create branch.The new branch (local to your system) will come on the left side along with the other existing branches, which you can push to the origin to get it to the repository, that way it becomes available to other users.
Comments
If you are looking for a command-line based solution, you can ignore my answer. I am gonna suggest you to use GitKraken. It's an extraordinary git UI client. It shows the Git tree on the homepage. You can just look at them and know what is going on with the project. Just select a specific commit, right-click on it and select the option 'Create a branch here'. It will give you a text box to enter the branch name. Enter branch name, select 'OK' and you are set. It's really very easy to use.
Comments
With GitHub Desktop, display the history pane and right click on the commit you want. Then choose the menu item "Create branch from commit".
Comments
I used Git Gui (which comes with Git for Windows).
- On the menu bar, open the Branch menu and select Create...
- Specify the name for the new branch in the Branch Name section
- Select Revision Expression: in the Start Revision section and enter the commit ID (I just used the 8 digit ID from Visual Studio and it worked)
Comments
If you use Sourcetree that is pretty straightforward.
- Right click the commit from where you need to create a new branch
- Click on 'branch'
- Type name of new branch in the dialog appeared and click 'create branch'






