pre-commit🔒 SSL Verified

Table of Contents

• ↓ Quick start ¶
• ↓ .pre-commit-config.yaml - top level ¶
• ↓ .pre-commit-config.yaml - repos ¶
• ↓ .pre-commit-config.yaml - hooks ¶
• ↓ Updating hooks automatically ¶
• ↓ Developing hooks interactively ¶
• ↓ Top Alternatives to pre-commit.com

6-Month Traffic Trend Estimate

Visual representation extracted from pre-commit.com

Content Snippets from pre-commit.com

"A framework for managing and maintaining multi-language pre-commit hooks."

"Git hook scripts are useful for identifying simple issues before submission to code review. We run our hooks on every commit to automatically point out issues in code such as missing semicolons, trailing whitespace, and debug statements. By pointing these issues out before code review, this allows a code reviewer to focus on the architecture of a change while not wasting time with trivial style nitpicks."

"As we created more libraries and projects we recognized that sharing our pre-commit hooks across projects is painful. We copied and pasted unwieldy bash scripts from project to project and had to manually change the hooks to work for different project structures."

"We believe that you should always use the best industry standard linters. Some of the best linters are written in languages that you do not use in your project or have installed on your machine. For example scss-lint is a linter for SCSS written in Ruby. If you’re writing a project in node you should be able to use scss-lint as a pre-commit hook without adding a Gemfile to your project or understanding how to get scss-lint installed."

Key Topics & Focus Areas for pre-commit.com:

Quick start ¶

.pre-commit-config.yaml - top level ¶

.pre-commit-config.yaml - repos ¶

.pre-commit-config.yaml - hooks ¶

Updating hooks automatically ¶

Developing hooks interactively ¶