You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See https://pre-commit.com/ website and various other technical sites for a more full description
Pre-commit hooks are scripts or actions that are run automatically before a commit is made to a version control system, such as Git. They serve as a quality control mechanism by allowing you to enforce certain checks and standards on the codebase before it is committed. Here are some reasons why including pre-commit hooks in a project can be beneficial:
Consistency
Code quality
Time savings
Continuous Integration
Codebase maintenance
collaboration
at the very minimun pre-commit hooks should apply code styling rules and file checking
repos:
- repo: https://github.com/pre-commit/pre-commit-hooksrev: v4.1.0hooks:
- id: check-added-large-files # prevents giant files from being committed.
- id: check-case-conflict # checks for files that would conflict in case-insensitive filesystems.
- id: check-merge-conflict # checks for files that contain merge conflict strings.
- id: check-yaml # checks yaml files for parseable syntax.
- id: detect-private-key # detects the presence of private keys.
- id: end-of-file-fixer # ensures that a file is either empty, or ends with one newline.
- id: fix-byte-order-marker # removes utf-8 byte order marker.
- id: mixed-line-ending # replaces or checks mixed line ending.
- id: requirements-txt-fixer # sorts entries in requirements.txt.
- id: trailing-whitespace # trims trailing whitespace.
The text was updated successfully, but these errors were encountered:
See https://pre-commit.com/ website and various other technical sites for a more full description
Pre-commit hooks are scripts or actions that are run automatically before a commit is made to a version control system, such as Git. They serve as a quality control mechanism by allowing you to enforce certain checks and standards on the codebase before it is committed. Here are some reasons why including pre-commit hooks in a project can be beneficial:
at the very minimun pre-commit hooks should apply code styling rules and file checking
see https://pre-commit.com/hooks.html for a list of pre-defined hooks (mirrors-prerrier for js)
other hooks could be:
The text was updated successfully, but these errors were encountered: