Adding upstream version 0.13.1.
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
parent
1805ece79d
commit
d8f166e6bb
167 changed files with 15302 additions and 0 deletions
87
examples/my_commit_rules.py
Normal file
87
examples/my_commit_rules.py
Normal file
|
@ -0,0 +1,87 @@
|
|||
from gitlint.rules import CommitRule, RuleViolation
|
||||
from gitlint.options import IntOption, ListOption
|
||||
from gitlint import utils
|
||||
|
||||
|
||||
"""
|
||||
The classes below are examples of user-defined CommitRules. Commit rules are gitlint rules that
|
||||
act on the entire commit at once. Once the rules are discovered, gitlint will automatically take care of applying them
|
||||
to the entire commit. This happens exactly once per commit.
|
||||
|
||||
A CommitRule contrasts with a LineRule (see examples/my_line_rules.py) in that a commit rule is only applied once on
|
||||
an entire commit. This allows commit rules to implement more complex checks that span multiple lines and/or checks
|
||||
that should only be done once per gitlint run.
|
||||
|
||||
While every LineRule can be implemented as a CommitRule, it's usually easier and more concise to go with a LineRule if
|
||||
that fits your needs.
|
||||
"""
|
||||
|
||||
|
||||
class BodyMaxLineCount(CommitRule):
|
||||
# A rule MUST have a human friendly name
|
||||
name = "body-max-line-count"
|
||||
|
||||
# A rule MUST have a *unique* id, we recommend starting with UC (for User-defined Commit-rule).
|
||||
id = "UC1"
|
||||
|
||||
# A rule MAY have an option_spec if its behavior should be configurable.
|
||||
options_spec = [IntOption('max-line-count', 3, "Maximum body line count")]
|
||||
|
||||
def validate(self, commit):
|
||||
line_count = len(commit.message.body)
|
||||
max_line_count = self.options['max-line-count'].value
|
||||
if line_count > max_line_count:
|
||||
message = "Body contains too many lines ({0} > {1})".format(line_count, max_line_count)
|
||||
return [RuleViolation(self.id, message, line_nr=1)]
|
||||
|
||||
|
||||
class SignedOffBy(CommitRule):
|
||||
""" This rule will enforce that each commit contains a "Signed-Off-By" line.
|
||||
We keep things simple here and just check whether the commit body contains a line that starts with "Signed-Off-By".
|
||||
"""
|
||||
|
||||
# A rule MUST have a human friendly name
|
||||
name = "body-requires-signed-off-by"
|
||||
|
||||
# A rule MUST have a *unique* id, we recommend starting with UC (for User-defined Commit-rule).
|
||||
id = "UC2"
|
||||
|
||||
def validate(self, commit):
|
||||
for line in commit.message.body:
|
||||
if line.startswith("Signed-Off-By"):
|
||||
return
|
||||
|
||||
return [RuleViolation(self.id, "Body does not contain a 'Signed-Off-By' line", line_nr=1)]
|
||||
|
||||
|
||||
class BranchNamingConventions(CommitRule):
|
||||
""" This rule will enforce that a commit is part of a branch that meets certain naming conventions.
|
||||
See GitFlow for real-world example of this: https://nvie.com/posts/a-successful-git-branching-model/
|
||||
"""
|
||||
|
||||
# A rule MUST have a human friendly name
|
||||
name = "branch-naming-conventions"
|
||||
|
||||
# A rule MUST have a *unique* id, we recommend starting with UC (for User-defined Commit-rule).
|
||||
id = "UC3"
|
||||
|
||||
# A rule MAY have an option_spec if its behavior should be configurable.
|
||||
options_spec = [ListOption('branch-prefixes', ["feature/", "hotfix/", "release/"], "Allowed branch prefixes")]
|
||||
|
||||
def validate(self, commit):
|
||||
violations = []
|
||||
allowed_branch_prefixes = self.options['branch-prefixes'].value
|
||||
for branch in commit.branches:
|
||||
valid_branch_name = False
|
||||
|
||||
for allowed_prefix in allowed_branch_prefixes:
|
||||
if branch.startswith(allowed_prefix):
|
||||
valid_branch_name = True
|
||||
break
|
||||
|
||||
if not valid_branch_name:
|
||||
msg = "Branch name '{0}' does not start with one of {1}".format(branch,
|
||||
utils.sstr(allowed_branch_prefixes))
|
||||
violations.append(RuleViolation(self.id, msg, line_nr=1))
|
||||
|
||||
return violations
|
Loading…
Add table
Add a link
Reference in a new issue