How can I reset or revert a file to a specific revision

Question

I have made some changes to a file which has been committed a few times as part of a group of files  but now want to reset revert the changes on it back to a previous version    I have done a git log along with a git diff to find the revision I need  but just have no idea how to get the file back to its former state in the past

User · Answer

git checkout -- foo   That will reset foo to HEAD  You can also   git checkout HEAD  foo   for one revision back  etc

User · Answer

git checkout -- foo   That will reset foo to HEAD  You can also   git checkout HEAD  foo   for one revision back  etc

User · Answer

git revert  lt hash gt    Will revert a given commit   It sounds like you think git revert only affects the most recent commit   That doesn t solve your problem  if you want to revert a change in a specific file and that commit changed more than that file

User · Answer

Use git log to obtain the hash key for specific version and then use git checkout  lt hashkey gt   Note  Do not forget to type the hash before the last one  Last hash points your current position  HEAD  and changes nothing

User · Answer

I have to plug EasyGit here  which is a wrapper to make git more approachable to novices without confusing seasoned users  One of the things it does is give more meanings to git revert  In this case  you would simply say   eg revert foo bar foo baz

User · Answer

You have to be careful when you say  rollback    If you used to have one version of a file in commit  A  and then later made two changes in two separate commits  B and  C  so what you are seeing is the third iteration of the file   and if you say  I want to roll back to the first one   do you really mean it     If  you want to get rid of the changes both the second and the third iteration  it is very simple     git checkout  A file   and then you commit the result   The command asks  I want to check out the file from the state recorded by the commit  A    On the other hand  what you meant is to get rid of the change the second iteration  i e  commit  B  brought in  while keeping what commit  C did to the file  you would want to revert  B    git revert  B   Note that whoever created commit  B may not have been very disciplined and may have committed totally unrelated change in the same commit  and this revert may touch files other than file you see offending changes  so you may want to check the result carefully after doing so

User · Answer

You have to be careful when you say  rollback    If you used to have one version of a file in commit  A  and then later made two changes in two separate commits  B and  C  so what you are seeing is the third iteration of the file   and if you say  I want to roll back to the first one   do you really mean it     If  you want to get rid of the changes both the second and the third iteration  it is very simple     git checkout  A file   and then you commit the result   The command asks  I want to check out the file from the state recorded by the commit  A    On the other hand  what you meant is to get rid of the change the second iteration  i e  commit  B  brought in  while keeping what commit  C did to the file  you would want to revert  B    git revert  B   Note that whoever created commit  B may not have been very disciplined and may have committed totally unrelated change in the same commit  and this revert may touch files other than file you see offending changes  so you may want to check the result carefully after doing so

User · Answer

Here is my way   a  In Android Studio  open the file   b  git -  Show History  find the previous commit I want to revert to  Get the commit id  i e  commit hash    c  git checkout commit id file path

User · Answer

Amusingly  git checkout foo will not work if the working copy is in a directory named foo  however  both git checkout HEAD foo and git checkout   foo will     pwd  Users aaron Documents work foo   git checkout foo D   foo Already on  foo    git checkout   foo   git checkout HEAD foo

User · Answer

In order to go to a previous commit version of the file  get the commit number  say eb917a1 then   git checkout eb917a1 YourFileName   If you just need to go back to the last commited version  git reset HEAD YourFileName git checkout YourFileName   This will simply take you to the last committed state of the file

User · Answer

git revert  lt hash gt    Will revert a given commit   It sounds like you think git revert only affects the most recent commit   That doesn t solve your problem  if you want to revert a change in a specific file and that commit changed more than that file

User · Answer

This worked for me   git checkout  lt commit hash gt  file   Then commit the change   git commit -a

User · Answer

Many suggestions here  most along the lines of git checkout  revision --  file  A couple of obscure alternatives   git show  revision  file  gt   file   And also  I use this a lot just to see a particular version temporarily   git show  revision  file   or  git show  revision  file   vim -R -    OBS   file needs to be prefixed with    if it is a relative path for git show  revision  file to work   And the even more weird   git archive  revision  file   tar -x0  gt   file

User · Answer

You have to be careful when you say  rollback    If you used to have one version of a file in commit  A  and then later made two changes in two separate commits  B and  C  so what you are seeing is the third iteration of the file   and if you say  I want to roll back to the first one   do you really mean it     If  you want to get rid of the changes both the second and the third iteration  it is very simple     git checkout  A file   and then you commit the result   The command asks  I want to check out the file from the state recorded by the commit  A    On the other hand  what you meant is to get rid of the change the second iteration  i e  commit  B  brought in  while keeping what commit  C did to the file  you would want to revert  B    git revert  B   Note that whoever created commit  B may not have been very disciplined and may have committed totally unrelated change in the same commit  and this revert may touch files other than file you see offending changes  so you may want to check the result carefully after doing so

User · Answer

For me none of the reply seemed really clear and therefore I would like to add mine which seems super easy    I have a commit abc1 and after it I have done several  or one modification  to a file file txt   Now say that I messed up something in the file file txt and I want to go back to a previous commit abc1   1 git checkout file txt   this will remove local changes  if you don t need them  2 git checkout abc1 file txt   this will bring your file to your wanted version  3 git commit -m  Restored file txt to version abc1    this will commit your reversion    git push   this will push everything on the remote repository    Between the step 2 and 3 of course you can do git status to understand what is going on  Usually you should see the file txt already added and that is why there is no need of a git add

User · Answer

You can quickly review the changes made to a file using the diff command   git diff  lt commit hash gt   lt filename gt    Then to revert a specific file to that commit use the reset command   git reset  lt commit hash gt   lt filename gt    You may need to use the --hard option if you have local modifications   A good workflow for managaging waypoints is to use tags to cleanly mark points in your timeline  I can t quite understand your last sentence but what you may want is diverge a branch from a previous point in time  To do this  use the handy checkout command   git checkout  lt commit hash gt  git checkout -b  lt new branch name gt    You can then rebase that against your mainline when you are ready to merge those changes   git checkout  lt my branch gt  git rebase master git checkout master git merge  lt my branch gt

User · Answer

If you know how many commits you need to go back  you can use   git checkout master 5 image png   This assumes that you re on the master branch  and the version you want is 5 commits back

User · Answer

Many suggestions here  most along the lines of git checkout  revision --  file  A couple of obscure alternatives   git show  revision  file  gt   file   And also  I use this a lot just to see a particular version temporarily   git show  revision  file   or  git show  revision  file   vim -R -    OBS   file needs to be prefixed with    if it is a relative path for git show  revision  file to work   And the even more weird   git archive  revision  file   tar -x0  gt   file

User · Answer

And to revert to last committed version  which is most frequently needed  you can use this simpler command   git checkout HEAD file to restore

User · Answer

Amusingly  git checkout foo will not work if the working copy is in a directory named foo  however  both git checkout HEAD foo and git checkout   foo will     pwd  Users aaron Documents work foo   git checkout foo D   foo Already on  foo    git checkout   foo   git checkout HEAD foo

User · Answer

Obviously someone either needs to write an intelligible book on git  or git needs to be better explained in the documentation   Faced with this same problem I guessed that   cd  lt working copy gt  git revert master   would undo the last commit which is seemed to do   Ian

User · Answer

In the case that you want to revert a file to a previous commit  and the file you want to revert already committed  you can use  git checkout HEAD 1 path to file   or  git checkout HEAD 1 path to file   Then just stage and commit the  new  version   Armed with the knowledge that a commit can have two parents in the case of a merge  you should know that HEAD 1 is the first parent and HEAD 1 is the second parent   Either will work if there is only one parent in the tree

User · Answer

You have to be careful when you say  rollback    If you used to have one version of a file in commit  A  and then later made two changes in two separate commits  B and  C  so what you are seeing is the third iteration of the file   and if you say  I want to roll back to the first one   do you really mean it     If  you want to get rid of the changes both the second and the third iteration  it is very simple     git checkout  A file   and then you commit the result   The command asks  I want to check out the file from the state recorded by the commit  A    On the other hand  what you meant is to get rid of the change the second iteration  i e  commit  B  brought in  while keeping what commit  C did to the file  you would want to revert  B    git revert  B   Note that whoever created commit  B may not have been very disciplined and may have committed totally unrelated change in the same commit  and this revert may touch files other than file you see offending changes  so you may want to check the result carefully after doing so

User · Answer

I have to plug EasyGit here  which is a wrapper to make git more approachable to novices without confusing seasoned users  One of the things it does is give more meanings to git revert  In this case  you would simply say   eg revert foo bar foo baz

User · Answer

git checkout ref commitHash -- filePath  e g    git checkout HEAD 5 -- foo bar or  git checkout 048ee28 -- foo bar

User · Answer

Use git log to obtain the hash key for specific version and then use git checkout  lt hashkey gt   Note  Do not forget to type the hash before the last one  Last hash points your current position  HEAD  and changes nothing

User · Answer

You can use any reference to a git commit  including the SHA-1 if that s most convenient  The point is that the command looks like this   git checkout  commit-ref  --  filename

User · Answer

Note  however  that git checkout   foo and git checkout HEAD   foo are not exactly the same thing  case in point     echo A  gt  foo   git add foo   git commit -m  A  foo Created commit a1f085f  A 1 files changed  1 insertions     0 deletions -  create mode 100644 foo   echo B  gt  gt  foo   git add foo   echo C  gt  gt  foo   cat foo A B C   git checkout   foo   cat foo A B   git checkout HEAD   foo   cat foo A    The second add stages the file in the index  but it does not get committed    Git checkout   foo means revert path   foo from the index  adding HEAD instructs Git to revert that path in the index to its HEAD revision before doing so

User · Answer

Here s how rebase works    git checkout  lt my branch gt  git rebase master git checkout master git merge  lt my branch gt       Assume you have   ---o----o----o----o  master      ---A----B        lt my branch gt     The first two commands     commit     git checkout      git rebase master      check out the branch of changes you want to apply to the master branch  The rebase command takes the commits from  lt my branch gt   that are not found in master  and reapplies them to the head of master  In other words  the parent of the first commit in  lt my branch gt  is no longer a previous commit in the master history  but the current head of master  The two commands are the same as   git rebase master  lt my branch gt    It might be easier to remember this command as both the  base  and  modify  branches are explicit     The final history result is    ---o----o----o----o   master                     ----A ----B    lt my branch gt       The final two commands      git checkout master git merge  lt my branch gt        do a fast-forward merge to apply all  lt my branch gt  changes onto master  Without this step  the rebase commit does not get added to master  The final result is    ---o----o----o----o----A ----B   master   lt my branch gt     master and  lt my branch gt  both reference B   Also  from this point it is safe to delete the  lt my branch gt  reference   git branch -d  lt my branch gt

User · Answer

Note  however  that git checkout   foo and git checkout HEAD   foo are not exactly the same thing  case in point     echo A  gt  foo   git add foo   git commit -m  A  foo Created commit a1f085f  A 1 files changed  1 insertions     0 deletions -  create mode 100644 foo   echo B  gt  gt  foo   git add foo   echo C  gt  gt  foo   cat foo A B C   git checkout   foo   cat foo A B   git checkout HEAD   foo   cat foo A    The second add stages the file in the index  but it does not get committed    Git checkout   foo means revert path   foo from the index  adding HEAD instructs Git to revert that path in the index to its HEAD revision before doing so

User · Answer

Obviously someone either needs to write an intelligible book on git  or git needs to be better explained in the documentation   Faced with this same problem I guessed that   cd  lt working copy gt  git revert master   would undo the last commit which is seemed to do   Ian

User · Answer

For me none of the reply seemed really clear and therefore I would like to add mine which seems super easy    I have a commit abc1 and after it I have done several  or one modification  to a file file txt   Now say that I messed up something in the file file txt and I want to go back to a previous commit abc1   1 git checkout file txt   this will remove local changes  if you don t need them  2 git checkout abc1 file txt   this will bring your file to your wanted version  3 git commit -m  Restored file txt to version abc1    this will commit your reversion    git push   this will push everything on the remote repository    Between the step 2 and 3 of course you can do git status to understand what is going on  Usually you should see the file txt already added and that is why there is no need of a git add

User · Answer

I think I ve found it    from http   www-cs-students stanford edu  blynn gitmagic ch02 html  Sometimes you just want to go back and forget about every change past a certain point because they re all wrong    Start with     git log  which shows you a list of recent commits  and their SHA1 hashes    Next  type     git reset --hard SHA1 HASH  to restore the state to a given commit and erase all newer commits from the record permanently

User · Answer

if you commit a wrong file in your last commits follow the instruction     open source tree  change to this commit      change the lines and find your commit that the wrong file sent as commit      you can see the list of your changes in that commit  select it and then click on     buttons right-hand side     click reverse file then you can see it on file status tab at the bottom left-hand side  then click unstage       open your visual studio code and revert back by committing your removed files after them all  you can see results in your last commit in the source tree

User · Answer

If you know how many commits you need to go back  you can use   git checkout master 5 image png   This assumes that you re on the master branch  and the version you want is 5 commits back

User · Answer

This is a very simple step  Checkout file to the commit id we want  here one commit id before  and then just git commit amend and we are done     git checkout  lt previous commit id gt   lt file name gt    git commit --amend   This is very handy  If we want to bring any file to any prior commit id at the top of commit  we can easily do

User · Answer

This is a very simple step  Checkout file to the commit id we want  here one commit id before  and then just git commit amend and we are done     git checkout  lt previous commit id gt   lt file name gt    git commit --amend   This is very handy  If we want to bring any file to any prior commit id at the top of commit  we can easily do

User · Answer

Assuming the hash of the commit you want is c5f567   git checkout c5f567 -- file1 to restore file2 to restore   The git checkout man page gives more information   If you want to revert to the commit before c5f567  append  1  where 1 is the number of commits you want to go back  it can be anything    git checkout c5f567 1 -- file1 to restore file2 to restore   As a side note  I ve always been uncomfortable with this command because it s used for both ordinary things  changing between branches  and unusual  destructive things  discarding changes in the working directory

User · Answer

git-aliases  awk and shell-functions to the rescue   git prevision  lt N gt   lt filename gt   where  lt N gt  is the number of revisions of the file to rollback for file  lt filename gt   For example  to checkout the immediate previous revision of a single file x y z c  run git prevision -1 x y z c   How git prevision works  Add the following to your gitconfig  alias          prevision    quot  f     git checkout  git log --oneline  2    awk -v commit  quot  1 quot   FNR    -commit 1  print  1     2    f quot    The command basically  performs a git log on the specified file and picks the appropriate commit-id in the history of the file and executes a git checkout to the commit-id for the specified file    Essentially  all that one would manually do in this situation  wrapped-up in one beautiful  efficient git-alias - git-prevision

User · Answer

git checkout ref commitHash -- filePath  e g    git checkout HEAD 5 -- foo bar or  git checkout 048ee28 -- foo bar

User · Answer

Amusingly  git checkout foo will not work if the working copy is in a directory named foo  however  both git checkout HEAD foo and git checkout   foo will     pwd  Users aaron Documents work foo   git checkout foo D   foo Already on  foo    git checkout   foo   git checkout HEAD foo

User · Answer

Assuming the hash of the commit you want is c5f567   git checkout c5f567 -- file1 to restore file2 to restore   The git checkout man page gives more information   If you want to revert to the commit before c5f567  append  1  where 1 is the number of commits you want to go back  it can be anything    git checkout c5f567 1 -- file1 to restore file2 to restore   As a side note  I ve always been uncomfortable with this command because it s used for both ordinary things  changing between branches  and unusual  destructive things  discarding changes in the working directory

User · Answer

In order to go to a previous commit version of the file  get the commit number  say eb917a1 then   git checkout eb917a1 YourFileName   If you just need to go back to the last commited version  git reset HEAD YourFileName git checkout YourFileName   This will simply take you to the last committed state of the file

User · Answer

You can use any reference to a git commit  including the SHA-1 if that s most convenient  The point is that the command looks like this   git checkout  commit-ref  --  filename

User · Answer

I had the same issue just now and I found this answer easiest to understand  commit-ref is the SHA value of the change in the log you want to go back to    git checkout  commit-ref   filename    This will put that old version in your working directory and from there you can commit it if you want

User · Answer

You can do it in 4 steps    revert the entire commit with the file you want to specifically revert - it will create a new commit on your branch soft reset that commit - removes the commit and moves the changes to the working area handpick the files to revert and commit them drop all other files in your work area   What you need to type in your terminal    git revert  lt commit hash gt  git reset HEAD 1 git add  lt file i want to revert gt   amp  amp  git commit -m  reverting file  git checkout     good luck

User · Answer

git revert  lt hash gt    Will revert a given commit   It sounds like you think git revert only affects the most recent commit   That doesn t solve your problem  if you want to revert a change in a specific file and that commit changed more than that file

User · Answer

As of git v2 23 0 there s a new git restore method which is supposed to assume part of what git checkout was responsible for  even the accepted answer mentions that git checkout is quite confusing   See highlights of changes on github blog   The default behaviour of this command is to restore the state of a working tree with the content coming from the source parameter  which in your case will be a commit hash    So based on Greg Hewgill s answer  assuming the commit hash is c5f567  the command would look like this   git restore --source c5f567 file1 to restore file2 to restore   Or if you want to restore to the content of one commit before c5f567   git restore --source c5f567 1 file1 to restore file2 to restore

User · Answer

I have to plug EasyGit here  which is a wrapper to make git more approachable to novices without confusing seasoned users  One of the things it does is give more meanings to git revert  In this case  you would simply say   eg revert foo bar foo baz

User · Answer

Many answers here claims to use git reset      lt file gt  or git checkout      lt file gt  but by doing so  you will loose every modifications on  lt file gt  committed after the commit you want to revert   If you want to revert changes from one commit on a single file only  just as git revert would do but only for one file  or say a subset of the commit files   I suggest to use both git diff and git apply like that  with  lt sha gt    the hash of the commit you want to revert     git diff  lt sha gt    lt sha gt  path to file ext   git apply -R   Basically  it will first generate a patch corresponding to the changes you want to revert  and then reverse-apply the patch to drop those changes   Of course  it shall not work if reverted lines had been modified by any commit between  lt sha1 gt  and HEAD  conflict

User · Answer

Here is my way   a  In Android Studio  open the file   b  git -  Show History  find the previous commit I want to revert to  Get the commit id  i e  commit hash    c  git checkout commit id file path

User · Answer

Assuming the hash of the commit you want is c5f567   git checkout c5f567 -- file1 to restore file2 to restore   The git checkout man page gives more information   If you want to revert to the commit before c5f567  append  1  where 1 is the number of commits you want to go back  it can be anything    git checkout c5f567 1 -- file1 to restore file2 to restore   As a side note  I ve always been uncomfortable with this command because it s used for both ordinary things  changing between branches  and unusual  destructive things  discarding changes in the working directory

User · Answer

First Reset Head For Target File  git reset HEAD path to file   Second Checkout That File  git checkout -- path to file

User · Answer

I have to plug EasyGit here  which is a wrapper to make git more approachable to novices without confusing seasoned users  One of the things it does is give more meanings to git revert  In this case  you would simply say   eg revert foo bar foo baz

User · Answer

I think I ve found it    from http   www-cs-students stanford edu  blynn gitmagic ch02 html  Sometimes you just want to go back and forget about every change past a certain point because they re all wrong    Start with     git log  which shows you a list of recent commits  and their SHA1 hashes    Next  type     git reset --hard SHA1 HASH  to restore the state to a given commit and erase all newer commits from the record permanently

User · Answer

Assuming the hash of the commit you want is c5f567   git checkout c5f567 -- file1 to restore file2 to restore   The git checkout man page gives more information   If you want to revert to the commit before c5f567  append  1  where 1 is the number of commits you want to go back  it can be anything    git checkout c5f567 1 -- file1 to restore file2 to restore   As a side note  I ve always been uncomfortable with this command because it s used for both ordinary things  changing between branches  and unusual  destructive things  discarding changes in the working directory

User · Answer

Note  however  that git checkout   foo and git checkout HEAD   foo are not exactly the same thing  case in point     echo A  gt  foo   git add foo   git commit -m  A  foo Created commit a1f085f  A 1 files changed  1 insertions     0 deletions -  create mode 100644 foo   echo B  gt  gt  foo   git add foo   echo C  gt  gt  foo   cat foo A B C   git checkout   foo   cat foo A B   git checkout HEAD   foo   cat foo A    The second add stages the file in the index  but it does not get committed    Git checkout   foo means revert path   foo from the index  adding HEAD instructs Git to revert that path in the index to its HEAD revision before doing so

User · Answer

git checkout -- foo   That will reset foo to HEAD  You can also   git checkout HEAD  foo   for one revision back  etc

User · Answer

Note  however  that git checkout   foo and git checkout HEAD   foo are not exactly the same thing  case in point     echo A  gt  foo   git add foo   git commit -m  A  foo Created commit a1f085f  A 1 files changed  1 insertions     0 deletions -  create mode 100644 foo   echo B  gt  gt  foo   git add foo   echo C  gt  gt  foo   cat foo A B C   git checkout   foo   cat foo A B   git checkout HEAD   foo   cat foo A    The second add stages the file in the index  but it does not get committed    Git checkout   foo means revert path   foo from the index  adding HEAD instructs Git to revert that path in the index to its HEAD revision before doing so

User · Answer

In the case that you want to revert a file to a previous commit  and the file you want to revert already committed  you can use  git checkout HEAD 1 path to file   or  git checkout HEAD 1 path to file   Then just stage and commit the  new  version   Armed with the knowledge that a commit can have two parents in the case of a merge  you should know that HEAD 1 is the first parent and HEAD 1 is the second parent   Either will work if there is only one parent in the tree

User · Answer

Amusingly  git checkout foo will not work if the working copy is in a directory named foo  however  both git checkout HEAD foo and git checkout   foo will     pwd  Users aaron Documents work foo   git checkout foo D   foo Already on  foo    git checkout   foo   git checkout HEAD foo

User · Answer

You can quickly review the changes made to a file using the diff command   git diff  lt commit hash gt   lt filename gt    Then to revert a specific file to that commit use the reset command   git reset  lt commit hash gt   lt filename gt    You may need to use the --hard option if you have local modifications   A good workflow for managaging waypoints is to use tags to cleanly mark points in your timeline  I can t quite understand your last sentence but what you may want is diverge a branch from a previous point in time  To do this  use the handy checkout command   git checkout  lt commit hash gt  git checkout -b  lt new branch name gt    You can then rebase that against your mainline when you are ready to merge those changes   git checkout  lt my branch gt  git rebase master git checkout master git merge  lt my branch gt

User · Answer

Many answers here claims to use git reset      lt file gt  or git checkout      lt file gt  but by doing so  you will loose every modifications on  lt file gt  committed after the commit you want to revert   If you want to revert changes from one commit on a single file only  just as git revert would do but only for one file  or say a subset of the commit files   I suggest to use both git diff and git apply like that  with  lt sha gt    the hash of the commit you want to revert     git diff  lt sha gt    lt sha gt  path to file ext   git apply -R   Basically  it will first generate a patch corresponding to the changes you want to revert  and then reverse-apply the patch to drop those changes   Of course  it shall not work if reverted lines had been modified by any commit between  lt sha1 gt  and HEAD  conflict

User · Answer

You can quickly review the changes made to a file using the diff command   git diff  lt commit hash gt   lt filename gt    Then to revert a specific file to that commit use the reset command   git reset  lt commit hash gt   lt filename gt    You may need to use the --hard option if you have local modifications   A good workflow for managaging waypoints is to use tags to cleanly mark points in your timeline  I can t quite understand your last sentence but what you may want is diverge a branch from a previous point in time  To do this  use the handy checkout command   git checkout  lt commit hash gt  git checkout -b  lt new branch name gt    You can then rebase that against your mainline when you are ready to merge those changes   git checkout  lt my branch gt  git rebase master git checkout master git merge  lt my branch gt

User · Answer

git revert  lt hash gt    Will revert a given commit   It sounds like you think git revert only affects the most recent commit   That doesn t solve your problem  if you want to revert a change in a specific file and that commit changed more than that file

User · Answer

git-aliases  awk and shell-functions to the rescue   git prevision  lt N gt   lt filename gt   where  lt N gt  is the number of revisions of the file to rollback for file  lt filename gt   For example  to checkout the immediate previous revision of a single file x y z c  run git prevision -1 x y z c   How git prevision works  Add the following to your gitconfig  alias          prevision    quot  f     git checkout  git log --oneline  2    awk -v commit  quot  1 quot   FNR    -commit 1  print  1     2    f quot    The command basically  performs a git log on the specified file and picks the appropriate commit-id in the history of the file and executes a git checkout to the commit-id for the specified file    Essentially  all that one would manually do in this situation  wrapped-up in one beautiful  efficient git-alias - git-prevision

User · Answer

Here s how rebase works    git checkout  lt my branch gt  git rebase master git checkout master git merge  lt my branch gt       Assume you have   ---o----o----o----o  master      ---A----B        lt my branch gt     The first two commands     commit     git checkout      git rebase master      check out the branch of changes you want to apply to the master branch  The rebase command takes the commits from  lt my branch gt   that are not found in master  and reapplies them to the head of master  In other words  the parent of the first commit in  lt my branch gt  is no longer a previous commit in the master history  but the current head of master  The two commands are the same as   git rebase master  lt my branch gt    It might be easier to remember this command as both the  base  and  modify  branches are explicit     The final history result is    ---o----o----o----o   master                     ----A ----B    lt my branch gt       The final two commands      git checkout master git merge  lt my branch gt        do a fast-forward merge to apply all  lt my branch gt  changes onto master  Without this step  the rebase commit does not get added to master  The final result is    ---o----o----o----o----A ----B   master   lt my branch gt     master and  lt my branch gt  both reference B   Also  from this point it is safe to delete the  lt my branch gt  reference   git branch -d  lt my branch gt

User · Answer

Git revert file to a specific commit    git checkout Last Stable commit Number -- fileName    2 Git revert file to a specific branch   git checkout branchName Which Has stable Commit fileName

User · Answer

git checkout -- foo   That will reset foo to HEAD  You can also   git checkout HEAD  foo   for one revision back  etc

User · Answer

if you commit a wrong file in your last commits follow the instruction     open source tree  change to this commit      change the lines and find your commit that the wrong file sent as commit      you can see the list of your changes in that commit  select it and then click on     buttons right-hand side     click reverse file then you can see it on file status tab at the bottom left-hand side  then click unstage       open your visual studio code and revert back by committing your removed files after them all  you can see results in your last commit in the source tree

User · Answer

As of git v2 23 0 there s a new git restore method which is supposed to assume part of what git checkout was responsible for  even the accepted answer mentions that git checkout is quite confusing   See highlights of changes on github blog   The default behaviour of this command is to restore the state of a working tree with the content coming from the source parameter  which in your case will be a commit hash    So based on Greg Hewgill s answer  assuming the commit hash is c5f567  the command would look like this   git restore --source c5f567 file1 to restore file2 to restore   Or if you want to restore to the content of one commit before c5f567   git restore --source c5f567 1 file1 to restore file2 to restore

User · Answer

And to revert to last committed version  which is most frequently needed  you can use this simpler command   git checkout HEAD file to restore

User · Answer

I had the same issue just now and I found this answer easiest to understand  commit-ref is the SHA value of the change in the log you want to go back to    git checkout  commit-ref   filename    This will put that old version in your working directory and from there you can commit it if you want

User · Answer

Git revert file to a specific commit    git checkout Last Stable commit Number -- fileName    2 Git revert file to a specific branch   git checkout branchName Which Has stable Commit fileName

User · Answer

First Reset Head For Target File  git reset HEAD path to file   Second Checkout That File  git checkout -- path to file

User · Answer

This worked for me   git checkout  lt commit hash gt  file   Then commit the change   git commit -a

User · Answer

If you re using Git Extensions and you only want to revert to the parent commit for the file  you can select the commit that contains the changes you want to revert  then select the  Diff  tab in the details pane  right-click the file you want to revert  then  Reset file s  to        then  A   the parent

User · Answer

If you re using Git Extensions and you only want to revert to the parent commit for the file  you can select the commit that contains the changes you want to revert  then select the  Diff  tab in the details pane  right-click the file you want to revert  then  Reset file s  to        then  A   the parent

User · Answer

I think I ve found it    from http   www-cs-students stanford edu  blynn gitmagic ch02 html  Sometimes you just want to go back and forget about every change past a certain point because they re all wrong    Start with     git log  which shows you a list of recent commits  and their SHA1 hashes    Next  type     git reset --hard SHA1 HASH  to restore the state to a given commit and erase all newer commits from the record permanently

User · Answer

You can quickly review the changes made to a file using the diff command   git diff  lt commit hash gt   lt filename gt    Then to revert a specific file to that commit use the reset command   git reset  lt commit hash gt   lt filename gt    You may need to use the --hard option if you have local modifications   A good workflow for managaging waypoints is to use tags to cleanly mark points in your timeline  I can t quite understand your last sentence but what you may want is diverge a branch from a previous point in time  To do this  use the handy checkout command   git checkout  lt commit hash gt  git checkout -b  lt new branch name gt    You can then rebase that against your mainline when you are ready to merge those changes   git checkout  lt my branch gt  git rebase master git checkout master git merge  lt my branch gt

User · Answer

You can do it in 4 steps    revert the entire commit with the file you want to specifically revert - it will create a new commit on your branch soft reset that commit - removes the commit and moves the changes to the working area handpick the files to revert and commit them drop all other files in your work area   What you need to type in your terminal    git revert  lt commit hash gt  git reset HEAD 1 git add  lt file i want to revert gt   amp  amp  git commit -m  reverting file  git checkout     good luck

User · Answer

I think I ve found it    from http   www-cs-students stanford edu  blynn gitmagic ch02 html  Sometimes you just want to go back and forget about every change past a certain point because they re all wrong    Start with     git log  which shows you a list of recent commits  and their SHA1 hashes    Next  type     git reset --hard SHA1 HASH  to restore the state to a given commit and erase all newer commits from the record permanently

[git] How can I reset or revert a file to a specific revision?

Examples related to git

Examples related to version-control

Examples related to git-checkout