> What are the advantages of using this plugin over using git in the terminal directly? Speaking generally to editor integrations and VCS GUI tools, the prime

> What are the advantages of using this plugin over using git in the terminal directly? Speaking generally to editor integrations and VCS GUI tools, the prime advantages vs. the CLI tools are: 1) Uninterrupted workflow for common tasks. Select files for commit, review the diffs, then commit all without leaving the editor. 2) Better visualization and interactive workflow. Examples include, good intra-line, side-by-side diff. Being able to `git blame` then trivially explore the associated commits and surrounding history for those commits. Yes, it's possible to do all of this from the command line, but it's often clunky compared to well-thought out tooling. With some VCS systems and projects, graphical display and navigation of history is helpful for understanding the relative state of branches, tracking down obscure bugs, etc. That said, I'm not a fan of glossy GUI tools that hide the working model of the underlying VCS. For the most part, not using the CLI is a great way to never really "get" version control as a powerful workflow tool. Perforce's P4V GUI tool gets credit on this point. The last time I used it, there was a console that showed the command line run and results for every GUI action. This happened to be a nice learning tool, providing relevant, live examples of basic and advanced usage.