In part one I showed how easy it is to version a project using Git from within Emacs, using the Magit package. This time we look at the git log within Magit.
Working with the log gives you a lot more detail about your changes, helps you compare local and remote repo commits. All of which helps you understand when you should push your code.
On the command line you can use git log to see your change history, although it can be a bit fiddly to set up git to give you a pretty view of those logs. In Magit you can just get on a explore the logs
Inside the Magit buffer, press
l to show the log menu and then either
l for the short for log or
L for the long form of the log.
l l - short log l L - long log
Selecting the short log details allows you to see more commits, but you only see the commit message and not the files that have changes.
In the following examples both the remote (github repository) and local repository are at the same commit -
e447b51. So you can easily tell if there are any local commits you have not pushed to Github.
Selecting the long log output,
l L, you see more details of each commit, including the files changed, author and timestamp.
To see the changes within a commit, move the cursor over a commit number in the log and press
space. This brings up another buffer which you can scroll through. You don’t even need to switch to this new buffer as if you keep pressing
space it will scroll through the text of the change.
The magit log also has a margin that shows the name and relative time of each commit. This can be very useful information to have at hand, although it does take up more space in the buffer.
To toggle the magit log margin, use
In the following example, the local repository is ahead of the Github repository by one commit. The magit log can be used to compare commits.
Move the cursor over the first commit and press
. (full stop). Then put the cursor over the second commit and press
To exit buffer that opened the diff, simply press
q in the Magit buffer.
I tend to just use the short form of the log and compare commits every now and again. If I havent pushed a few commits up to Github for a while, its a handy way to check if I should push and what I am pushing.
Of course if I write good commit messages and commit often to my local repo, then its much easier to tell what I am pushing from just the short log.
This work is licensed under a Creative Commons Attribution 4.0 ShareAlike License, including custom images & stylesheets. Permissions beyond the scope of this license may be available at @jr0cket