-
Notifications
You must be signed in to change notification settings - Fork 26
/
.gitlint
41 lines (32 loc) · 1.59 KB
/
.gitlint
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
[general]
# Ignore certain rules, you can reference them by their id or by their full name
ignore=body-is-missing,body-min-length
# verbosity should be a value between 1 and 3, the commandline -v flags take precedence over this
# verbosity = 2
# Enable debug mode (prints more output). Disabled by default.
# debug=true
# By default gitlint will ignore merge commits. Set to 'false' to disable.
ignore-merge-commits=true
# By default gitlint will ignore fixup commits. Set to 'false' to disable.
ignore-fixup-commits=false
# By default gitlint will ignore squash commits. Set to 'false' to disable.
ignore-squash-commits=false
[title-max-length]
line-length=80
# [title-must-not-contain-word]
# Comma-separated list of words that should not occur in the title. Matching is case
# insensitive. It's fine if the keyword occurs as part of a larger word (so "WIPING"
# will not cause a violation, but "WIP: my title" will.
# words=wip
[title-match-regex]
# python like regex (https://docs.python.org/2/library/re.html) that the
# commit-msg title must be matched to.
# Note that the regex can contradict with other rules if not used correctly
# (e.g. title-must-not-contain-word).
regex=^[^:]+: [^:]+ .*$
#[body-changed-file-mention]
# List of files that need to be explicitly mentioned in the body when they are changed
# This is useful for when developers often erroneously edit certain files or git submodules.
# By specifying this rule, developers can only change the file when they explicitly reference
# it in the commit message.
#files=.buildkite/pipeline.yml,.buildkite/build,.buildkite/lint,.buildkite/check,README.md