diff options
| author | Daniel R. Carvalho <odanrc@yahoo.com.br> | 2019-09-29 14:06:04 +0200 |
|---|---|---|
| committer | Daniel Carvalho <odanrc@yahoo.com.br> | 2019-12-06 10:15:24 +0000 |
| commit | 451ff4aa048628effe3f3ba6e2c42080bb4612fa (patch) | |
| tree | 1113233fbe1240fd175b0da093640ee08c1d2c17 /ext | |
| parent | 4bbd03d76d2e03324f94ba23abcd20ab5e66feec (diff) | |
| download | gem5-451ff4aa048628effe3f3ba6e2c42080bb4612fa.tar.xz | |
util: Add a git commit-msg hook
Add a git commit-msg hook that verifies that commit messages follow
gem5 guidelines.
Commit messages must contain the following components:
<gem5_tags>: <title>
<description>
<patch_tags>
<gem5_tags> are comma separated keywords (found in MAINTAINERS) that
describe which sections of gem5 are being modified by the patch.
Two special keywords can also be used to imply that the author is
looking for feedback on the way their commit was implemented (RFC),
and to inform that the commit is a work in progress (WIP).
<title> A short and concise description of the commit without trailing
whitespaces
<description> is an optional (yet highly recommended) detailed
description of the objective of the commit.
<patch_tags> describe the metadata of the commit, and most of them
are automatically added by Gerrit.
Change-Id: Ib6fb6edf6d1417bfda23729b35c5b8ed44d2cf51
Signed-off-by: Daniel R. Carvalho <odanrc@yahoo.com.br>
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/21739
Reviewed-by: Bobby R. Bruce <bbruce@ucdavis.edu>
Maintainer: Bobby R. Bruce <bbruce@ucdavis.edu>
Tested-by: kokoro <noreply+kokoro@google.com>
Diffstat (limited to 'ext')
| -rwxr-xr-x | ext/git-commit-msg | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/ext/git-commit-msg b/ext/git-commit-msg index 60fe59da7..db83fd73c 100755 --- a/ext/git-commit-msg +++ b/ext/git-commit-msg @@ -189,3 +189,6 @@ _gen_ChangeId() { add_ChangeId + +# Perform gem5-specific commit message style check +./util/git-commit-msg.py $MSG |