You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that in this game, even though you "delete" a commit you don't stop to see the commit, even this commit is died. But, in this level, you explain that you can make a dangerous git reset --hard, for example, to the first commit, and then you can change the order of the previous commits with cherry-picking but, in "real life" this commits are already gone. You can't access to this commits because you killed them all with git reset --hard. I thing the only correct way to pass the level is using git rebase -i.
Now, I have to say that I'm a student and maybe I'm wrong with this. Pls, if you can, tell me if this is correct or I'm wrong and exist a way to make git reset --hard and then operate with the "previous later" commits.
Thanks for reading me!
The text was updated successfully, but these errors were encountered:
I understand that in this game, even though you "delete" a commit you don't stop to see the commit, even this commit is died. But, in this level, you explain that you can make a dangerous git reset --hard, for example, to the first commit, and then you can change the order of the previous commits with cherry-picking but, in "real life" this commits are already gone. You can't access to this commits because you killed them all with git reset --hard. I thing the only correct way to pass the level is using git rebase -i.
Now, I have to say that I'm a student and maybe I'm wrong with this. Pls, if you can, tell me if this is correct or I'm wrong and exist a way to make git reset --hard and then operate with the "previous later" commits.
Thanks for reading me!
The text was updated successfully, but these errors were encountered: