#Git create branch on commit how to#

You can make the working copy of your git repository match the state in that commit by running The first 8 characters will be enough to uniquely identify the hash, so weвЂ™ll use ca41886d in the example. For this example, we will pretend the hash for that commit is ca41886daca7f55aa7d88a5ae7b226dd3e670739. For example, the hash for the commit with the log message вЂњpluto is not a planet.вЂќ. Run git log and pick the commit hash for any of the old commits. To do this, you need the commit hash from running git log. You can also restore a specific state from your history by checking out that commit. You will see that the git history in branch-master contains all of the commits from the other branches, with exactly the same commit messages and hashes. To confirm this, compare the commit hashes that you see when you run git log master against the commit hashes in each of the other branches. Now that youвЂ™ve merged your work into the main master branch, you can delete all of the other branches without losing any history because the master branch actually contains all of the work from all of the branches, including the entire history of changes. Step: Confirm that the master branch has your whole history With the branch-master branch checked out, merge the work from branch-a to branch-master by running $ git checkout -b branch-master Step: Start merging the work into the fake вЂњmasterвЂќ branch Now create a new вЂњbranch-masterвЂќ branch where we will combine everyoneвЂ™s work $ git checkout planets-before-merge-conflict To create the fake вЂњmasterвЂќ branch, checkout the planets-before-merge-conflict branch which contains the original version of planets.md by running This will let us compare all of the stages of the process before we finish. In normal use, you would merge these changes into the master branch, but for the purposes of this exercise we will create a fake вЂњmasterвЂќ branch. On branch-a there is a commit with the message вЂњsets the correct number of planetsвЂќ while on branch-b there is a commit with the message вЂњpluto is not a planet.вЂќ the commit messages are different AND the commit hashes are different. When you compare these two commits, you should see that both of them have the original commit with the message вЂњplanets.md before merge conflictвЂќ and that commit hash is the same in both branches but each branch has a different commit after this one. What should we do if we want to keep these changes or go back to the previous one? We'll see in the next point.Output the commit history for each branch by running

It shows that now HEAD is pointing to the latest commit 7a367ef: Below is the graphical representation of the commits done on top of HEAD. LetвЂ™s run git log вЂ“oneline and see the result: $ git log -onelineД§a367ef (HEAD) Add a new line to the fileД«efore HEAD was pointing to the 5282c7c commit, then we added two more commits, d423c8c and 7a367ef. We now have two additional commits that descend from our second commit. Git commit -a -m 'Add a new line to the file'

#Git create branch on commit how to#

LetвЂ™s review how to do it using the below commands: echo 'understanding git detached head scenarios' > sample-file.txt What if we could take not only a look at the past but also change it? ThatвЂ™s what a detached HEAD allows us to do. Then we can check out the commit and test the application, either by hand or by running our automated test suite. We can use the log command, filtering by date, to start the relevant commit hash. LetвЂ™s say we want to check if a given bug already existed last Tuesday. Since we've checkout to a previous commit, now the HEAD is pointing to 5282c7c commit, and the master branch is still referring to the same: 4. : MINGW64 ~/git/detached-head-demo ((5282c7c.))Д«elow is the graphical representation of the current git HEAD.

HEAD is now at 5282c7c appending more info If you want to create a new branch to retain commits you create, you mayДo so (now or later) by using -c with the switch command. State without impacting any branches by switching back to a branch. You can look around, make experimentalД¬hanges and commit them, and you can discard any commits you make in this However, after running the below command the repo is in a detached HEAD: $ git checkout 5282c7c All of that means, in the above scenarios, HEAD is synonymous with вЂњthe last commit in the current branch.вЂќ This is the normal state in which HEAD is attached to a branch:ДЄs we can see, HEAD points to the master branch, which points to the last commit. When we change branches, HEAD is updated to point to the branch we've switched to. When we add a new commit, our branch reference is updated to point to it, but HEAD remains the same. For most of the time, HEAD points to a branch name.