Chore: Upgrade Jenkins-job-builder to 6.2.0
[releng/global-jjb.git] / .pre-commit-config.yaml
1 ---
2 repos:
3   - repo: https://github.com/pre-commit/pre-commit-hooks
4     rev: v4.5.0
5     hooks:
6       - id: trailing-whitespace
7       - id: no-commit-to-branch
8         args:
9           - --branch=master
10           - --branch=main
11
12   - repo: https://github.com/pre-commit/mirrors-prettier
13     rev: v4.0.0-alpha.8
14     hooks:
15       - id: prettier
16         stages: [commit]
17
18   - repo: https://github.com/jorisroovers/gitlint
19     rev: v0.19.1
20     hooks:
21       - id: gitlint
22
23   - repo: https://github.com/adrienverge/yamllint.git
24     rev: v1.35.1
25     hooks:
26       - id: yamllint
27
28   - repo: https://github.com/jumanjihouse/pre-commit-hooks
29     rev: 3.0.0
30     hooks:
31       - id: shellcheck
32
33   - repo: https://github.com/btford/write-good
34     rev: v1.0.8
35     hooks:
36       - id: write-good
37         exclude: >
38           (?x)^(
39             docs/jjb/lf-c-cpp-jobs.rst|
40             docs/jjb/lf-ci-jobs.rst|
41             docs/jjb/lf-macros.rst|
42             docs/jjb/lf-python-jobs.rst
43           )$
44
45   - repo: https://github.com/btford/write-good
46     rev: v1.0.8
47     hooks:
48       # Files listed below break the following write-good rules:
49       #   - adverb weakens meaning
50       #   - is wordy or unneeded
51       #
52       # This allows us to place an exception needed to pass the check without
53       # disabling all checks for the whole file. In an ideal world write-good
54       # would give us an override for each individual instance of a violation
55       # but until then this gives us a close enough approach.
56       - id: write-good
57         name: "write-good --no-adverb --no-tooWordy"
58         args: ["--no-adverb", "--no-tooWordy"]
59         files: docs/jjb/lf-ci-jobs.rst
60
61   - repo: https://github.com/btford/write-good
62     rev: v1.0.8
63     hooks:
64       # Files listed below break the following write-good rules:
65       #   - is wordy or unneeded
66       #
67       # This allows us to place an exception needed to pass the check without
68       # disabling all checks for the whole file. In an ideal world write-good
69       # would give us an override for each individual instance of a violation
70       # but until then this gives us a close enough approach.
71       - id: write-good
72         name: "write-good --no-tooWordy"
73         args: ["--no-tooWordy"]
74         files: >
75           (?x)^(
76             docs/jjb/lf-c-cpp-jobs.rst|
77             docs/jjb/lf-macros.rst|
78             docs/jjb/lf-python-jobs.rst
79           )$