Question 1

How do I skip a hook in Overcommit?

Accepted Answer

Use the SKIP environment variable with the hook name, e.g., SKIP=RuboCop git commit. For a whitelist, use ONLY, or set required: true in config to prevent skipping entirely.

Question 2

Overcommit vs Husky: which is better?

Accepted Answer

Overcommit is Ruby-based with extensive built-in hooks and parallel execution, ideal for Ruby teams needing deep Git integration. Husky is Node.js-focused, lighter, and easier for JavaScript ecosystems. Choose based on your stack and hook complexity.

Question 3

How to add a custom script as a hook in Overcommit?

Accepted Answer

In .overcommit.yml, define a hook with required_executable pointing to your script. Overcommit executes it with appropriate Git arguments, and success depends on exit status, as shown in the 'Adding Existing Git Hooks' section.

Question 4

Does Overcommit work on Windows?

Accepted Answer

Overcommit has best-effort support for Windows but is primarily designed for *nix systems. Some hooks may not function correctly, and Ruby runtime issues can arise, as noted in the Requirements section.

Question 5

How to run Overcommit hooks in continuous integration?

Accepted Answer

Use the overcommit --run command to execute pre-commit hooks against all tracked files, returning a non-zero exit code if any hook fails, making it CI-ready as described in the Continuous Integration section.

Question 6

What's the deal with signature verification in Overcommit?

Accepted Answer

It warns when hook code or configuration changes to prevent malicious execution. You must sign initially with overcommit --sign, and it can be disabled via verify_signatures: false, but this reduces security.

Overcommit

What is Overcommit?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions