Magit is a text-based Git user interface that puts an unmatched focus on streamlining workflows. Commands are invoked using short mnemonic key sequences that take the cursor’s position in the highly actionable interface into account to provide context-sensitive behavior.
With Magit you can do nearly everything that you can do when using Git on the command-line, but at greater speed and while taking advantage of advanced features that previously seemed too daunting to use on a daily basis. Many users will find that by using Magit they can become more effective Git user.
Please consider supporting the ongoing crowd-funding campaign. If it succeeds, then I can work full-time on Magit for a whole year. I am still overflowing with ideas, and depend on your support to realize them, and to address the remaining long-standing issues. Thank you!
On the occasion of the Kickstarter campaign, I have written the following articles.
If you are completely new to Magit, then this article is a good visual introduction.
Almost everything that you see in Magit can be acted on by pressing some key, but that’s not obvious from just seeing how Magit looks. The screenshots and accompanying text of this article explain how to perform a variety of actions on Magit’s output.
Magit differs significantly from other Git interfaces, and its advantages are not immediately obvious simply from looking at a few screenshots as presented in the preceding article.
This article discusses Magit’s properties in somewhat more abstract terms.
Unfortunately, most potential users are not even aware of Magit. Others might be aware of its existence but would not consider giving it a try because it is implemented as an extension to the Emacs text editor, and that’s not what they are using.
This article discusses why Magit can be an excellent Git interface even if you don’t use Emacs for editing purposes and gives a preview of how I intend to make Magit more accessible to non-Emacs users.
Visit Magit’s homepage for additional resources, including screencasts, blog posts, user testimonals, and the manual.