2
You could walk yourself through the project by rebasing it interactively:
$ git rebase -i <sha of the first commit>
This will open an editor (by default – vi) with all the project’s commits and an instruction of what git should do with them. The default is, of course, pick
. You could change all the pick
s to edit
s (in vi: :%s/^pick/edit/
), save, and quit the editor (in vi: :wq
).
Now, git will rebase the entire project, one commit at a time, and return control to you after it applies each commit. So each commit, you’ll get the prompt back, and would be able to read the current state of the code, deploy it, debug it, etc. When you’re satisfied you understand the current commit, just use git rebase --continue
to move on to the next one.
Source:stackexchange.com