Git Commands I Always Forget
April 16, 2020 · 4 min read
I share one trick a day until the original scheduled date of the end of the COVID-19 quarantine in Switzerland, April 19th 2020. Three days left until this first milestone. Hopefully better days are ahead.
When it comes to Git, I probably rely too much on its really well-made integration of my editor, WebStorm. This has for consequence, that I sometimes forget useful commands, even simple ones, which I only have rarely to run in my terminal.
That’s why I am sharing this blog post mostly for my future self 😅.
Revert Last Commit
To revert your last commit if it has not been pushed yet, you can rewind the history from a step back with the help of the
However, if your commit has already been pushed, you can preserve your history and run a
revert command (where
eec47301 is the revision number of the commit to revert which can be found for example with the help of the
git log command) followed by a commit and push.
git revert eec47301
Alternatively revert it without preserving the history with the help of the
reset command and the option
--hard followed by a push with the option
git reset --hard eec47301
Needless to say, it has to be use wisely.
Change Last Commit Message
If your last commit message was wrong or if you had for example a typo, you can modify the last, or most recent, commit message with the option
git commit --amend
If your commit has not been pushed yet, nothing else to do. To the contrary, if you already have pushed it, you can update your repo with
git push --force
Change Multiple Commit Messages
If you are looking to amend multiple commit messages, which might happens for example if you did forget to specify the related issue number, you can proceed with the help of
To start amending we run the following command where
2 is the number of commits on which we want to perform a
git rebase -i HEAD~2
This will open a prompt which will allow us to specify changes on each commits.
pick e68a142 my frst update pick 1613f1e my scnd update
As we want to change the commit message, we modify
reword (or the short version
reword e68a142 my frst update reword 1613f1e my scnd update
Once done, we save (
:wq ) and the prompt will automatically guide us to the first selected commit we would like to change.
my frst update
We can correct the message (
x to delete a character,
is to switch to insert mode,
aa to append and always
Esc escape editing mode), save it and the prompt will again automatically guide us to the next commit message we would like to change and so on.
my snd update
Once finished, our terminal will look like the following:
❯ git rebase -i HEAD~2 [detached HEAD 1f02610] my first update Date: Thu Apr 16 15:55:09 2020 +0200 1 file changed, 1 insertion(+), 1 deletion(-) [detached HEAD 68d3edd] my second update Date: Thu Apr 16 16:00:29 2020 +0200 1 file changed, 4 insertions(+) Successfully rebased and updated refs/heads/master.
At this point our history is locally rewritten but not yet updated in our repo, that’s why we push these.
git push --force
If you would face problems while running the above process, you would be able to cancel the rebase operation using
git rebase --abort
Speaking of abort, it is also possible to quit a merge while using the same option.
git merge --abort
Delete A Tag
When you delete a release on GitHub, it does delete it but it does not delete the related tag. Typically, if you go back to your repo with your browser, it is still displayed.
If you would like to remove such tags, you can do so with the help of a Git push and the option
--delete followed by the name of the tag to remove.
git push --delete origin v0.0.1
Hopefully this time I will remember these command lines but if not, at least I will know where to find them 😁.
Stay home, stay safe!