Honestly out of the box Git management for VSCode is really good. I'm surprised how quickly it got integrated to my regular workflow, and I'm a terminal gitter to boot.

The ability to see side by side diffs and which files/lines I've touched is what did it for me. I still use git CLI for squashing, rebasing etc, but basic staging and committing I do entirely in VSCode now.

I've been very satisfied with https://github.com/divmain/GitSavvy and GitGutter. Together they are how I do almost all of my git.

another vote for gitgutter. jumping to the next changed hunk in my currently open file is a life-changer.

https://github.com/jisaacks/GitGutter

If you want git support out of the box, please give me a thumbs up on this PR. https://github.com/sublimehq/Packages/pull/1126 If you can read sublime-syntax files, code review is appreciated as well.

With this package, you can set Sublime to be your git editor like this:

  $ cat ~/.gitconfig
  [core]
    editor = subl -w
  ...

GitGutter and GitSavvy have been fantastic for my Git mileage -- have you tried them?

I prefer VSCode mostly for the intellisense/auto-complete.

As far as git is concerned, I use it from the command line an cannot understand why anyone would want to interact with git from VSCode or any other text editor.

I don't know if these editors support it, but being able to access git blame from editor is convenient, also the editor can highlight all the changes you've done since the last revision (especially useful to hunt down unnecessary whitespace changes).

I think Will Bond has a git plugin that's supposed to be pretty good. I don't like VCS plugins in my editor though, so I've never tried it.

Text editors shouldn't come with hardware requirements.

All software has hardware requirements.

Even ed has hardware requirements.