Skip to content

Latest commit

 

History

History
59 lines (35 loc) · 3.88 KB

history.md

File metadata and controls

59 lines (35 loc) · 3.88 KB

History

git: log

Opens a panel with a chronological list of all ancestors of the current commit. To find a particular commit, you can start typing either the commit hash (the shortened form is included), or the first line of the commit message itself. What you type will be fuzzy-string matched against the commit records by Sublime. Author and age information is included, but not directly searchable with this command.

By default, the list is paginated at 6,000 commits for performance reasons. To view the next 6,000 commits, start typing >>> NEXT. Whens selected, you will see a list with the next 6,000 commits.

On selection of a commit you can choose from the following options:

  • Show commit: Display the commit.
  • Compare commit against working directory: Display the diff between the commit and the working directory.
  • Compare commit against index: Display the diff between the commit and staged changes in the index.

git: log current file

Performs a similar function to git: log, but restricts your search to the history of the currently open file. Has additional option upon selection of a commit:

  • Show file at commit: Display the file at the time of the commit.

git: log by author

Performs a similar function to git: log, but restricts your search to a particular committer. When run, you will be prompted for the name and/or email of the committer you're searching for - the field will be pre-populated with your own name and email. The full name/email is not required for the search to succeed.

git: blame current file

A GitHub-style blame view is displayed. Each hunk of the file will be shown on the right, with the associated commit info shown to its left. This includes the beginning of the commit message, commit hash, author, and age.

Pressing SUPER-Enter (CTRL-Enter in Windows) while your cursor is inside a hunk will take you to that specific commit.

Blame options

When run, you will be prompted for how you want the blame view to search for changes:

Default

Use default git blame behaviour.

Ignore whitespace

Ignore whitespace only changes when finding the last commit that changed the line (git blame -w).

Detect moved or copied lines within same file

Ignore whitespace, and detect when lines have been moved or copied within the file, attributing lines to the original commit rather than the commit that moved or copied them (git blame -w -M).

Detect moved or copied lines within same commit

Ignore whitespace, and detect when lines have been moved or copied from any file modified in the same commit, attributing lines to the original commit rather than the commit that moved or copied them (git blame -w -C).

Detect moved or copied lines across all commits

Ignore whitespace, and detect when lines have been moved or copied from any file across the full commit history of the repository, attributing lines to the original commit rather than the commit that moved or copied them (git blame -w -CCC).

git: graph current branch

Opens a special view that displays an ASCII-graphic representation of the repo's commit and branch history.

Use . to go to next commit and use , to go to previous commit.

Pressing m while your cursor is over a particular line will toggle display of a quick panel containing more info about the selected commit. If you've changed your is graph_show_more_commit_info settting to false, the quick panel will not display automatically.

Pressing Enter while your cursor is over a particular line will display the commit reflected on that line. Pressing SUPER-Enter (CTRL-Enter in Windows) will check out the commit. Note that a successful commit will not be visually reflected in the graph view.

git: graph all branches

Same as git: graph current branch. The only difference is that we add '--all' flag to the command. This will show all commits and stashes on all branches.