arxanas/git-branchless

High-velocity, monorepo-scale workflow for Git

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 58 minutes ago
Added to GitGenius on September 16th, 2026
Created on December 10th, 2020
Open Issues & Pull Requests: 95 (+0)
GitHub issues: Enabled
Number of forks: 116
Total Stargazers: 4,127 (+0)
Total Subscribers: 16 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 35.0 hours
Mean response time: 71.5 days
90th percentile: 225.0 days
Tracked items: 53

Most active contributors

Sign in to see contributor activity.

How this project is maintained

84% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 86% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 32
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 788 days
Stale 30+ days: 30
Stale 90+ days: 26

Recent activity

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

Top labels

  • bug (44)
  • enhancement (11)
  • good first issue (10)
  • help wanted (7)
  • has-workaround (3)
  • no-planned-fix (2)

Most active issues this week

Sign in to see which issues are moving.

Detailed Description

git-branchless is a Git workflow tool that optimizes development velocity in monorepo environments by streamlining branch management and commit organization.

The tool addresses the friction of managing many concurrent branches and commits in large codebases. It works by providing commands that abstract away low-level Git operations, allowing developers to focus on logical changes rather than branch mechanics. The approach emphasizes rapid iteration through features like automatic branch tracking, simplified rebasing, and streamlined commit navigation, reducing the cognitive overhead of maintaining complex branch hierarchies.

Teams working in monorepos or those making frequent commits across multiple features should consider this tool. It suits developers who find traditional Git workflows cumbersome when juggling many parallel changes. The project is particularly valuable for high-velocity teams where branch management becomes a bottleneck rather than a convenience. Developers accustomed to linear commit histories or those working on smaller projects with simpler branching patterns may find the tool's complexity unnecessary for their workflow.

The project shows sustained active development with regular commits addressing both new features and bug fixes. Maintenance is responsive, with issues and pull requests receiving timely attention. The codebase demonstrates careful attention to user experience, with incremental improvements to command interfaces and error messaging. Development activity indicates a commitment to stability alongside feature expansion, suggesting the tool is treated as a production system rather than an experimental prototype.