sds/overcommit

A fully configurable and extendable Git hook manager

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Type:CLI ToolCategory(s):Git & Version ControlDeveloper Tools
Added to GitGenius on September 17th, 2026
Created on March 24th, 2011
Open Issues & Pull Requests: 35 (+0)
GitHub issues: Enabled
Number of forks: 287
Total Stargazers: 4,004 (+0)
Total Subscribers: 82 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.7 days
Mean response time: 263.4 days
90th percentile: 980.4 days
Tracked items: 15

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 779 days
Stale 30+ days: 6
Stale 90+ days: 6

Recent activity

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

Top labels

  • bug (3)
  • help wanted (2)
  • question (1)

Most active issues this week

Detailed Description

Overcommit is a Git hook manager that allows you to configure and manage Git hooks across repositories through a centralized, extensible system.

The tool solves the problem of managing Git hooks consistently and flexibly by providing a configuration-driven approach. Rather than manually maintaining hook scripts in each repository's .git directory, Overcommit lets you define hooks in source-controlled configuration files that apply across multiple repositories. It supports a wide variety of built-in hooks covering different Git lifecycle events, and you can add your own hook scripts without writing Ruby code. The system allows both shared hooks and repository-specific hooks, with options for skipping individual hooks, running hooks concurrently, and integrating with continuous integration workflows.

Teams should adopt Overcommit if they want centralized control over Git hook behavior across projects while maintaining the flexibility to customize hooks per repository. It works well for teams using Ruby-based projects or those already managing dependencies with Bundler, since many hooks have third-party dependencies that can be specified in a Gemfile. The tool is particularly suited for projects that need consistent linting, commit message validation, or pre-push checks enforced across multiple repositories without duplicating configuration.

Development activity in the project is dominated by bug reports and user questions in the issue tracker, indicating an established tool with an active user base seeking fixes and clarification rather than new features.