Go to particular revision

Question

I cloned a git repository of a certain project  Can I turn the files to the initial state and when I review the files go to revision 2  3  4     most recent  I d like to have an overview of how the project was evolving

User · Answer

To check a commit out  nb you are looking at the past      git checkout  commmitHash    To brutally restart from a commit and delete those later branches that you probably messed up    git reset --hard  commmitHash

User · Answer

You can get a graphical view of the project history with tools like gitk  Just run   gitk --all   If you want to checkout a specific branch   git checkout  lt branch name gt    For a specific commit  use the SHA1 hash instead of the branch name   See Treeishes in the Git Community Book  which is a good read  to see other options for navigating your tree    git log has a whole set of options to display detailed or summary history too   I don t know of an easy way to move forward in a commit history  Projects with a linear history are probably not all that common  The idea of a  revision  like you d have with SVN or CVS doesn t map all that well in Git

User · Answer

Using a commit s SHA1 key  you could do the following    First  find the commit you want for a specific file   git log -n  lt   commits gt   lt file-name gt   This  based on your  lt   commits gt   will generate a list of commits for a specific file   TIP  if you aren t sure what commit you are looking for  a good way to find out is using the following command  git diff  lt commit-SHA1 gt   HEAD  lt file-name gt    This command will show the difference between the current version of a commit  and a previous version of a commit for a specific file   NOTE  a commit s SHA1 key is formatted in the git log -n s list as        commit  lt SHA1 id gt     Second  checkout the desired version   If you have found the desired commit version you want  simply use the command  git checkout  lt desired-SHA1 gt   lt file-name gt   This will place the version of the file you specified in the staging area   To take it out of the staging area simply use the command  reset HEAD  lt file-name gt    To revert back to where the remote repository is pointed to  simply use the command  git checkout HEAD  lt file-name gt

User · Answer

Before executing this command keep in mind that it will leave you in detached head status Use git checkout  lt sha1 gt  to check out a particular commit  Where  lt sha1 gt  is the commit unique number that you can obtain with git log Here are some options after you are in detached head status   Copy the files or make the changes that you need to a folder outside your git folder  checkout the branch were you need them git checkout  lt existingBranch gt  and replace files Create a new local branch git checkout -b  lt new branch name gt   lt sha1 gt

User · Answer

To get to a specific committed code  you need the hash code of that commit  You can get that hash code in two ways    Get it from your github gitlab bitbucket account    It s on your commit url  i e  github com user my project commit commit hash code   or you can git log and check your recent commits on that branch  It will show you the hash code of your commit and the message you leaved while you were committing your code  Just copy and then do git checkout commit hash code   After moving to that code  if you want to work on it and make changes  you should make another branch with git checkout -b  lt new-branch-name gt   otherwise  the changes will not be retained

User · Answer

To go to a particular version commit run following commands  HASH-CODE you can get from git log --oneline -n 10  git reset --hard HASH-CODE   Note - After reset to particular version commit you can run git pull --rebase  if you want to bring back all the commits which are discarded

User · Answer

One way would be to create all commits ever made to patches  checkout the initial commit and then apply the patches in order after reading    use git format-patch  lt initial revision gt  and then git checkout  lt initial revision gt   you should get a pile of files in your director starting with four digits which are the patches    when you are done reading your revision just do git apply  lt filename gt  which should look like  git apply 0001-  and count   But I really wonder why you wouldn t just want to read the patches itself instead  Please post this in your comments because I m curious   the git manual also gives me this    git show next 10 Documentation README       Shows the contents of the file Documentation README as they were current in the 10th last commit of the branch next    you could also have a look at git blame filename which gives you a listing where each line is associated with a commit hash   author

User · Answer

I was in a situation where we have a master branch  and then another branch called 17 0 and inside this 17 0 there was a commit hash no say  XYZ   And customer is given a build till that XYZ revision  Now we came across a bug and that needs to be solved for that customer  So we need to create separate branch for that customer till that  xyz  hash  So here is how I did it   First I created a folder with that customer name on my local machine  Say customer name is  AAA  once that folder is created issue following command inside this folder    git init git clone  After this command you will be on master branch  So switch to desired branch git checkout 17 0 This will bring you to the branch where your commit is present git checkout  This will take your repository till that hash commit  See the name of ur branch it got changed to that commit hash no  Now give a branch name to this hash git branch ABC This will create a new branch on your local machine  git checkout ABC git push origin ABC This will push this branch to remote repository and create a branch on git server  You are done

[git] Go to particular revision

Examples related to git

Examples related to revision

Examples related to revision-history