To push up through a given commit, you can write: git push <remotename> <commit SHA>:<remotebranchname> provided <remotebranchname> already exists on the remote. (If it doesn’t, you can use git push <remotename> <commit SHA>:refs/heads/<remotebranchname> to autocreate it.) If you want to push a commit without pushing previous commits, you should first use git rebase -i to … Read more
The –follow works for a particular file git log –follow — filename Difference to other solutions given Note that other solutions include git log path (without the –follow). That approach is handy if you want to track e.g. changes in a directory, but stumbles when files were renamed (thus use –follow filename).
Changing history If it is the most recent commit, you can simply do this: git commit –amend This brings up the editor with the last commit message and lets you edit the message. (You can use -m if you want to wipe out the old message and use a new one.) Pushing And then when … Read more
Expanding what I wrote in a comment The general rule is that you should not rewrite (change) history that you have published, because somebody might have based their work on it. If you rewrite (change) history, you would make problems with merging their changes and with updating for them. So the solution is to create … Read more
What you need to do is to create a new commit with the same details as the current HEAD commit, but with the parent as the previous version of HEAD. git reset –soft will move the branch pointer so that the next commit happens on top of a different commit from where the current branch … Read more