tpope / vim-fugitive
git clone https://github.com/tpope/vim-fugitive.git
🔥 on GitHub Trending today
fugitive.vim: A Git wrapper so awesome, it should be illegal
+2
stars, 24h · #513
—
stars, 7 days
+44
stars, 30 days · #6,559
22k
★ total
1.1k
forks · 101 open issues
Star history starts 2026-10-20; the chart appears after the second daily snapshot.
LanguageVim Script
License—
Created2009-10-09 (17y ago)
Last push7mo ago
Watchers221
OwnerUser
Seen on GitHub Trending
- 2026-10-20 — #5 daily in vim-script · +2 ★
- 2026-10-20 — #6 monthly in vim-script · +44 ★
Links
- GitHub: github.com/tpope/vim-fugitive
- Homepage: https://www.vim.org/scripts/script.php?script_id=2975
- Releases · Issues · Hacker News mentions
README excerpt
# fugitive.vim Fugitive is the premier Vim plugin for Git. Or maybe it's the premier Git plugin for Vim? Either way, it's "so awesome, it should be illegal". That's why it's called Fugitive. The crown jewel of Fugitive is `:Git` (or just `:G`), which calls any arbitrary Git command. If you know how to use Git at the command line, you know how to use `:Git`. It's vaguely akin to `:!git` but with numerous improvements: * The default behavior is to directly echo the command's output. Quiet commands like `:Git add` avoid the dreaded "Press ENTER or type command to continue" prompt. * `:Git commit`, `:Git rebase -i`, and other commands that invoke an editor do their editing in the current Vim instance. * `:Git diff`, `:Git log`, and other verbose, paginated commands have their output loaded into a temporary buffer. Force this behavior for any command with `:Git --paginate` or `:Git -p`. * `:Git blame` uses a temporary buffer with maps for additional triage. Press enter on a line to view the commit where the line changed, or `g?` to see other available maps. Omit the filename argument and the currently edited file will be blamed in a vertical, scroll-bound split. * `:Git mergetool` and `:Git difftool` load their changesets into the quickfix list. * Called with no arguments, `:Git` opens a summary window with dirty files and unpushed and unpulled commits. Press `g?` to bring up a list of maps for numerous operations including diffing, staging, committing, rebasing, and stashing. (This is the successor to the old `:Gstatus`.) * This command (along with all other commands) always uses the current buffer's repository, so you don't need to worry about the current working directory. Additional commands are provided for higher level operations: * View any blob, tree, commit, or tag in the repository with `:Gedit` (and `:Gsplit`, etc.). For example, `:Gedit HEAD~3:%` loads the current file as it existed 3 commits ago. * `:Gdiffsplit` (or `:Gvdiffsplit`) brings up the staged version of the file side by side with the working tree version. Use Vim's diff handling capabilities to apply changes to the staged version, and write that buffer to stage the changes. You can also give an arbitrary `:Gedit` argument to diff against older versions of the file. * `:Gread` is a variant of `git checkout -- filename` that operates on the buffer rather than the file itself. This means you can use `u` to undo it and you never get any warnings about the file changing outside Vim. * `:Gwrite` writes to both the work tree and index versions of a file, making it like `git add` when called from a work tree file and like `git checkout` when called from the index or a blob in history. * `:Ggrep` is `:grep` for `git grep`. `:Glgrep` is `:lgrep` for the same. * `:GMove` does a `git mv` on the current file and changes the buffer name to match. `:GRename` does the same with a destination filename relative to the current file's directory. * `:GDelete` does a `git rm