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
{{ message }}
This repository has been archived by the owner on Jul 19, 2023. It is now read-only.
I would like to propose a rule which checks for the existing of a pre-commit configuration file. The content of the file will vary from repo to repo, but the presence of such a file indicates that pre-commit hooks are managed in the repo.
Further extension of the rule could be that there must be a stage in the pipeline which executes these checks, in case the committer has not enabled them in their clone of the repo.
Similar to #105, this can also ensure that a commit message syntax is enforced via commitlint
The rule needs to, at a minimum, assert the presence and correctness of .pre-commit-config.y[a]ml
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would like to propose a rule which checks for the existing of a pre-commit configuration file. The content of the file will vary from repo to repo, but the presence of such a file indicates that pre-commit hooks are managed in the repo.
Further extension of the rule could be that there must be a stage in the pipeline which executes these checks, in case the committer has not enabled them in their clone of the repo.
Similar to #105, this can also ensure that a commit message syntax is enforced via commitlint
The rule needs to, at a minimum, assert the presence and correctness of
.pre-commit-config.y[a]ml
The text was updated successfully, but these errors were encountered: