tpope/vim-fugitive

fugitive.vim: A Git wrapper so awesome, it should be illegal

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 15 minutes ago
Added to GitGenius on September 2nd, 2026
Created on October 9th, 2009
Open Issues & Pull Requests: 137 (+0)
GitHub issues: Enabled
Number of forks: 1,079
Total Stargazers: 21,777 (+0)
Total Subscribers: 224 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 63
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 472 days
Stale 30+ days: 61
Stale 90+ days: 52

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (2)
  • unconfirmed (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

vim-fugitive is a Git wrapper for Vim that integrates version control operations directly into the editor.

The tool solves the friction of switching between Vim and Git command-line tools by embedding Git functionality within the editor itself. It works by providing Vim commands that map to Git operations, allowing developers to stage changes, view diffs, browse commit history, and resolve merge conflicts without leaving their editing session. The wrapper exposes Git's capabilities through an interface designed for Vim's modal editing paradigm.

Developers working primarily in Vim should adopt this tool if they want to reduce context switching during version control tasks. It suits any project using Git, from solo work to team collaboration. The tool is particularly valuable for developers who spend extended periods in Vim and want Git operations to feel native to their workflow rather than external commands.

The project maintains a steady stream of commits addressing bug fixes and incremental feature additions. Pull requests receive thoughtful review and discussion before integration. The maintainer responds to issues with detailed explanations and often provides guidance on workarounds or alternative approaches when changes cannot be immediately implemented. Development activity shows consistent engagement with the user base rather than sporadic bursts of work.