Skip to content

About

Example repository showing conflict between pre-commit check-hooks-apply and forbid-new-submodules

Resources

Stars

1 star

Watchers

1 watching

Forks

Latest commit

 

History

4 Commits

Folders and files

Repository files navigation

forbid-new-submodules is not useless!

This repo is an example showing the behavior of pre-commit hooks check-hooks-apply and forbid-new-submodules.

Using this .pre-commit-config.yaml:

repos:
  - repo: meta
    hooks:
      - id: check-hooks-apply
  - repo: https://github.com/pre-commit/pre-commit-hooks
    rev: v4.3.0
    hooks:
      - id: forbid-new-submodules

Results in the following error during pre-commit run:

$ pre-commit run --all-files
Check hooks apply to the repository......................................Failed
- hook id: check-hooks-apply
- exit code: 1

forbid-new-submodules does not apply to this repository

forbid new submodules................................(no files to check)Skipped

About

Example repository showing conflict between pre-commit check-hooks-apply and forbid-new-submodules

Resources

Stars

1 star

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages