magicmonty/bash-git-prompt

An informative and fancy bash prompt for Git users

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 44 minutes ago
Added to GitGenius on September 9th, 2026
Created on December 4th, 2012
Open Issues & Pull Requests: 35 (+0)
GitHub issues: Enabled
Number of forks: 982
Total Stargazers: 6,939 (+0)
Total Subscribers: 151 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.0 days
Mean response time: 102.9 days
90th percentile: 187.1 days
Tracked items: 12

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 734 days
Stale 30+ days: 9
Stale 90+ days: 7

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Detailed Description

bash-git-prompt is a bash prompt customization that displays detailed information about the current Git repository state.

The tool solves the problem of having limited visibility into your Git working directory by displaying branch name, staging status, and synchronization with remote branches directly in your prompt. It works by parsing Git repository metadata and rendering symbolic indicators for common states: staged files, unstaged changes, merge conflicts, stash entries, and commits ahead or behind the remote branch. The prompt shows these details inline using Unicode symbols, allowing you to see your repository status at a glance without running separate Git commands.

The tool suits developers who work frequently with Git from the command line and want immediate feedback on repository state. It works with both bash and fish shells. Installation is straightforward via Homebrew on macOS or by cloning the repository and sourcing it in your shell configuration. The prompt is highly configurable: you can disable untracked file counting for repositories with many build artifacts, show or hide the upstream branch name, and choose from different visual themes. The README does not compare it to alternatives.

The project maintains active engagement with bug reports and feature requests. Pull requests receive review and integration. The codebase has been refined through community contributions addressing edge cases and performance concerns. Development activity shows responsiveness to issues affecting usability in different Git workflows and shell environments.