There are several ways to make a commit, both through the status view and through the command palette.
This command can be invoked by both the command palette and the status dashboard, and opens a special view where you can make a commit. The view includes instructions for how to complete and how to abort the action.
GitHub integration is provided to provide easy access to issues and contributors. More information can be found in their respective sections.
This command is similar to the above git: commit command. However, once you have provided the commit message, all unstaged changes will be added to the index before the commit is made.
This command is similar to the above git: commit command. However, instead of creating a new commit, this command will modify the previous command.
The commit view will be pre-populated with the previous commit message. Proceeding will update the commit message, and the commit's diff will be amended with any changes present in the index.
This command is used to fixup an earlier commit from already staged files. A list of commits of the current branch will be shown and upon selection, the fixup will be squashed into the select commit. If autosquash fails, it leaves a fixup commit fixup! <original commit> in the log.
When invoking this palette command, Sublime will prompt you for a one-line commit message (you will not see the GitSavvy commit view). Pressing Enter will invoke the commit action, and pressing Escape will abort.
This command is only available via the command palette.
When invoking this palette command, Sublime will prompt you for a one-line commit message. Before making the commit, the currently open file will be staged and included in the subsequent commit.
Keep in mind that any other changes that have been staged will also be included in the commit. This command is only available via the command palette.
Similar to git: amend previous commit. This command also stages the current file before amending the commit.
Similar to git: fixup from stage. This command also stages the current file before fixing up the commit.
You can automatically sign your commits depending on your configuration.
GitHub has instructions on how to add your GPG key to GitHub and configure git to use your key.
If you always want to sign your commits with a GPG key you can configure git globally, locally in your git repo or using the global_pre_flags setting.:
git config (--global) commit.gpgsign true
When you commit with GitSavvy it will attempt to sign your commit. If your key hasn't been unlocked yet with your passphrase you will be asked for it (see more on credentials below).
For more information, see official git docs on the subject.
GitSavvy does not support prompting a user for credentials (there is no way, known to us, to forward the password securely to git). In order to tell git to ask for your passphrase through the OS gui, you can set the askPass variable in your config, e.g:
git config (--global) core.askPass git-gui--askpass
For more information, see official git docs on the subject.