Previously I opened a shell inside Emacs and ran the
hub createcommand to create a new remote Github repository for a project. This worked, but not the same speed as having a feature built-in to Magit itself.
An effective way to have a clean and valuable commit history is to create the smallest valuable commit each time, with a descriptive commit message. This sounds obvious, but when you are in the midst of work things can get messy. Using Emacs Magit you can be highly selective as to what changes you include in each commit, down to individual characters.
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.
Getting to grips with Git was not to much of a learning curve, although I found it quicker to work on the command line than using graphical tools. Using
git status and
git log made it easy to keep a handle on my code changes.
As I do most of my Clojure development in Emacs, it was great to discover I could drive git from Emacs using Magit. What follows is a flow through the first steps with Magit.
In part two I look at Git logs with Magit