GitSavvy is a powerful and mature plugin for Sublime Text that brings most of Git's functionalities directly into the text editor.

It offers features that just come naturally when in an editor. For example, you can easily interactively stage or discard changes per hunk, per line, per file. Search for specific content that you just select right in the buffer. Navigate through the history of commits and revisions of files, write clear and long(!) commit messages (because who wants to deal with a clunky input box in a separate program for that?). GitSavvy makes standard rebasing actions, like rewording a commit message, trivial, and advanced rebasing techniques, such as splitting a feature branch into two, manageable.

However, GitSavvy enhances your Git experience. It does not replace it.

1. Install the Sublime Text Package Control plugin if you don't have it already.
2. Open the command palette and start typing Package Control: Install Package.
3. Enter GitSavvy.

If you want more control over what you pull down, or if you'd like to submit changes to GitSavvy (👈👌), you should clone the repository directly in the Packages folder and restart the editor. You still have to run Package Control: Satisfy Dependencies after that!

Note: GitSavvy requires Git versions at or greater than 2.18.0. However, it is highly recommended to use a more recent version of Git, as some advanced rebasing features in GitSavvy require at least version 2.38.0. Upgrading to the latest version of Git will ensure that you can take full advantage of all the features and improvements available in GitSavvy.

Note: GitSavvy does not support Sublime Text 2. If you are using Sublime Text 3, you can access the last supported version by checking out the st3-2.39.1 tag. That's to say, the current main line of GitSavvy only supports Sublime Text versions above build 4000. For the best experience, use the latest Sublime Text dev build. Or not, I mean it could also crash you, what am I to recommend here.

When you first install GitSavvy, you may not notice any immediate changes to your Sublime Text interface. Except that you may see the checked out branch name and dirty status displayed in the status bar. (You can change this in the settings if you want to.) It's important to note that GitSavvy actually adds a lot of commands to Sublime's Command Palette, which can be accessed by pressing ctrl+shift+p on Windows or cmd+shift+p on macOS. These commands are typically prefixed with git: , while all GitHub features are prefixed with github: .

GitSavvy also comes with dedicated views. In order to get started with GitSavvy, it's a good idea to become familiar with the git: status and git: Repo History views first. These views are a great entry point into the GitSavvy world and will help you get comfortable with the plugin before diving deeper into its other features. (In fact, I did not venture beyond the git: status view for the first year or so but hey, GitSavvy also changed a lot since then.)

By default, the status view shows some helpful information, while in the repo history view, you can get additional help by pressing [?]. The most important keys to remember in the repo history view are [enter] for the main menu and [r] for the rebase menu.

GitSavvy provides all the essential Git commands such as clone, init, commit, checkout, pull, push, fetch, and many more.

All of these commands and features can be accessed easily through Sublime's Command Palette (ctrl+shift+p). Just start typing the name of the command you want to use, e.g. checkout, and Sublime will quickly select the correct command. You can recognize GitSavvy commands as they are all prefixed with git: .

After you hit enter to select a command, GitSavvy will often start a wizard. For example, typing checkout will show a list of available branches, while typing checkout new branch will ask for the name of the new branch. Note that Sublime's fuzzy logic helps with typing long commands and remembers acronyms you've used in the Command Palette. For instance, on my computer, typing chn followed by enter is enough to create a new branch.

GitSavvy provides dedicated views for Git status, branches, and tags. Users can access these views by running the git: status, git: branch commands.

In addition to these views, GitSavvy also has sophisticated special views for viewing diffs and patches, making commits, or showing the repository history. However, for new users, running the git: status command may be the first entry point into the GitSavvy world. From here, you can stage ([s]), unstage ([u]), and discard ([d]) changes to whole files. You can also start the commit phase ([c]), open the repository history ([g]), open a diff view ([f]), and push the current branch ([p]).

Tip: if nothing has been staged yet, pressing [c] will default to committing all changes with the -a flag.

Note that views with smaller content like the status view typically display their keyboard bindings directly at the bottom of the screen, while views with larger content, e.g. the repo history, will only show the key bindings in a help popup after you press [?].

GitSavvy comes with a lot of keyboard bindings, but it doesn't include any global shortcuts. This is because adding global shortcuts can conflict with other packages or built-in functionality. However, you can easily add your own global shortcuts by opening Sublime's key bindings file (Preferences: Key Bindings).

For example, you can add a global shortcut to open the status view from anywhere by adding the following to your key bindings file:

{ "keys": ["ctrl+shift+s"], "command": "gs_show_status"}

This will allow you to quickly access the Git status view with the ctrl+shift+s shortcut, no matter what file or view you have open. You can add other shortcuts for other GitSavvy commands in a similar way.

After checking the git status, the second most common action is probably to make a commit. So it is a good idea to make a shortcut here as well. Simply add the following code to Sublime's keybindings:

{ "keys": ["ctrl+shift+c"], "command": "gs_commit"},

gs_commit will open up the commit view in GitSavvy. If nothing is staged yet, it will assume the -a flag and select all changes. However, it will not include untracked files as is typical with Git. Within the commit view, you always see the diff of the changes to be committed at the bottom. Here, you can easily unstage or discard hunks or single lines directly using the keyboard shortcuts [u] and [d]. Note that you can undo a discard by pressing ctrl+z.

Sometimes you may want to find out which commands to use, along with their optional arguments. You can use Sublime's console, which is a Python REPL, to help you with this.

To open the console in Sublime, press Ctrl + ` on Windows or Linux, or Cmd + ` on a Mac. This will open a panel at the bottom of the window where you can enter commands.

To enable logging of commands, enter the following command in the console:

sublime.log_commands(True)

This will cause Sublime to log all commands executed by the user in the console.

Now, start GitSavvy's Command Palette (ctrl+shift+p) and run a command, such as git: status. After the command has executed, look at the console to see the name of the command and any optional arguments that were passed.

For example, you might see:

command: gs_commit {"amend": true}

Here, gs_commit is the name of the command, and the optional argument passed was {"amend": true}. This information can be useful for learning and customizing GitSavvy's functionality.

Don't forget to turn off command logging when you're done, by entering:

sublime.log_commands(False)

in the console.

GitSavvy's Repo History view provides a visual representation of a repository's commit history and is accessible via the git: Repo History command. It's similar to gitk but with more features. When editing a tracked file, you can alternatively use git: File History to open a file-specific history view. But you can also turn any standard Repo History view into a file/folder history view and vice versa by using [l] which opens up a list of all tracked files.

The Repo History view offers additional filtering options. Press [a] to toggle between showing all branches or only the currently checked out branch. Press [f] to open the filter prompt, where you can add filters verbatim, like --author= or -Sfoobar. You can use the up and down arrow keys to access a list of default filters or to see the history of filters you've previously used. Once you've filtered the graph, you can quickly toggle the filter on and off using [F].

Press [s] to enter a special "overview" mode showing only the tip of the branches and the tags. ([a] in that mode will toggle the tags on and off too.)

To move around the commit graph, you can either use your mouse or the up and down arrow keys. If you want to make larger jumps in the graph, you can use the keyboard shortcut alt+up or alt+down, which jumps through the "first-parent" only.

The Repo History view has two main menus. Pressing [enter] will open the standard menu, which provides typical functionality such as checking out, cherry-picking, or reverting the currently selected commit. You can also find basic branch and tag functionality like creating or deleting them. Additionally, you can move branch pointers around (as opposed to resetting) or update branches from their upstream.

You can access a second menu by pressing [r], which is specifically designed for rebasing. This menu allows you to reword commit messages ([W]), edit ([E]) or drop commits, apply fixups, and generally rebase anything onto anything. For example, you can extract a series of commits onto your main branch to make two feature branches out of a convoluted one.

Note the visual connection between fixup commits and the commits they are associated with.	When the cursor is positioned on a fixup (or squash) commit, the `[r]`ebase menu will provide a specific action to apply that fixup.

You can review any rebase afterwards. E.g.

Open the `[r]`ebase menu again. (The currently checked out branch is named "which" here.)	Show the previous tip of the currently checked out branch side by side.	Showing the main menu, maybe show a diff between both variants or undo by selecting "Move ...".

If you encounter merge conflicts that need to be resolved manually, displaying the diff can help ensure that you haven't introduced any unintended changes or made mistakes. (In most cases, the diff will be empty, indicating that both tips are identical in terms of code.) From the main menu you can also choose to "Move" or to "Reset" the branch back to the previous tip, effectively undoing the rebase. "Move" will simply move the branch label, while "Reset" performs your typical reset operation that can also modify Git's staging area and discard uncommitted changes, depending on the mode you choose. Usually choose "Move" here to undo a rebase.

GitSavvy has a feature called "Line History," also known as git's "wtf?" view. This allows you to view the commit history of specific lines within the repository. It's a great way to quickly research the history of a particular piece of code before using the traditional blame view.

To access Line History, you can start on any normal view by selecting some lines, such as a function, and then issuing the git: Line History command from the command palette. But really, you can start on any diff/patch that GitSavvy shows you.

To make it more seamless, I recommend, again, to make a shortcut. For example, you can add the following to your user keybindings:

  { "keys": ["ctrl+shift+l"], "command": "gs_line_history"},

Once you have that, you can use ctrl+l to select some lines, followed by ctrl+shift+l to follow those lines.

GitSavvy will then show you snippets of commits/patches to show you the evolution of those lines. [o] on such an excerpt will open the complete commit. [O] will display the version of the file as it existed at that specific point in time. And [f] for example will initiate a fixup commit for the commit under the cursor. (Either with the stage, or with all changes if nothing is staged yet, as usual.)

Tip: The Line History is also available from any view where we show a diff or patch. (It is thus available from within the Line History views.) On such a view you don't necessarily have to select any lines, as it will select the current hunk for you by default, giving you the "hunk-history", so to speak.

Even deeper: After [o] or [O] you can navigate around in time with [n] (next) and [p] (previous). You can show the commit's context using [g], and the hunks context by opening the inline diff. That's easier with more keybindings:

  { "keys": ["ctrl+shift+,"], "command": "gs_inline_diff" },
  { "keys": ["ctrl+shift+."], "command": "gs_diff", "args": {"current_file": true} },

That's pretty crazy, right? All views are connected, and you can really navigate around the history.

GitSavvy provides a git diff view that allows users to stage, unstage, and reset (discard) files, hunks, or individual lines.

GitSavvy offers fixup/squash helpers that can be accessed from various views, including the "Line History" view.

GitSavvy provides GitHub integration that allows users to reference issues/collaborators when committing, open the current file or a commit on GitHub at the selected line, and create a new pull request from the current branch.

GitSavvy offers a "blame" view that shows hunk metadata and allows users to view the commit that made the change, similar to GitHub's blame view.

The documentation is probably outdated. Yeah it's sad but you can contribute and I will eventually get onto it but every special view has help available, just press ?.

Feature documentation can be found here. It can also be accessed from within Sublime by opening the command palette and typing GitSavvy: help.

Status dashboard	Tags dashboard
Display and overview and offer actions to manipulate your project state.	View and manipulate local and remote tags.

Diff
Stage, unstage or discard hunks, files or individual lines. (video)

Github integration
Reference issues and collaborators in commits. Open files on GitHub in the browser, with lines pre-selected. Create pull requests. Fork a repository.