Github desktop revert commit results in >>> HEAD even in a new cloned repository

Question

I try to revert a commit on Github Desktop. There was conflicts so I deleted the whole project and cloned it again to have a completely fresh clone.

Still after I reverted the commit I get things like ">>> HEAD". Why can't it just go back to previous commit?

I've made an animated gif of what I do:

score 1 · Accepted Answer · answered Jun 30 '18 at 21:34

You are reverting—i.e., asking Git to undo—the changes from a commit that is not the most recent commit.

If you intend to revert to that commit, i.e., to undo the changes that came after that commit, you should revert the subsequent commit.

score 1 · Answer 2 · answered Jun 30 '18 at 22:51

1

You seem to be misunderstanding GIT,

Still after I reverted the commit I get things like ">>> HEAD". Why can't it just go back to previous commit?

What you mean: Lets go back 1 entry in the revision history

What you try to do: Revert changes from the 2th revision change

You should revert the top commit, that way you go back 1 version in time.

answered Jun 30 '18 at 22:51

Ferrybig

If I understand it correctly, if I need to back 10 commits, I should back 10 times with the most recent first? – Jens Törnell Jul 02 '18 at 05:34

2 Answers2