mirrors
/
git-validation
mirror of https://github.com/vbatts/git-validation.git
1
0
Fork 0
Code Releases Activity
utility for validating git commits (in a CI like travis or jenkins)
82 Commits 1 Branch 4 Tags 147 KiB
Go 100%
Go to file
Vincent Batts 59392066c4
main: add support for github actions 
Fixes #48

now with logic to detect GITHUB_SHA env variable, let's do a run without
the `-range` flag so that path lights up.

Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
 		2021-05-14 14:17:58 -04:00
.github/workflows main: add support for github actions 2021-05-14 14:17:58 -04:00
git Consider only commit IDs when listing range 2020-09-16 11:41:22 -04:00
rules shortsubject: merge commits may be long 2017-11-15 11:59:18 -05:00
validate message_regexp: regular expression rule for messages 2017-10-09 16:07:40 -04:00
.gitignore Initial commit 2015-10-05 18:48:23 -04:00
.travis.yml Update travis to supported Go versions 2020-03-26 23:23:26 -04:00
LICENSE Initial commit 2015-10-05 18:48:23 -04:00
README.md Updated usage of GIT_CHECK_EXCLUDE 2018-03-07 09:54:54 +09:00
go.mod Add go module support 2019-05-06 14:38:14 +02:00
go.sum Add go module support 2019-05-06 14:38:14 +02:00
main.go main: add support for github actions 2021-05-14 14:17:58 -04:00

README.md

git-validation

A way to do validation on git commits. Build Status

install

vbatts@valse ~ (master) $ go get -u github.com/vbatts/git-validation

usage

The flags

vbatts@valse ~/src/vb/git-validation (master *) $ git-validation -h
Usage of git-validation:
  -D    debug output
  -d string
        git directory to validate from (default ".")
  -list-rules
        list the rules registered
  -range string
        use this commit range instead
  -run string
        comma delimited list of rules to run. Defaults to all.
  -v    verbose

The entire default rule set is run by default:

vbatts@valse ~/src/vb/git-validation (master) $ git-validation -list-rules
"dangling-whitespace" -- checking the presence of dangling whitespaces on line endings
"DCO" -- makes sure the commits are signed
"message_regexp" -- checks the commit message for a user provided regular expression
"short-subject" -- commit subjects are strictly less than 90 (github ellipsis length)

Or, specify comma-delimited rules to run:

vbatts@valse ~/src/vb/git-validation (master) $ git-validation -run DCO,short-subject
 * b243ca4 "README: adding install and usage" ... PASS
 * d614ccf "*: run tests in a runner" ... PASS
 * b9413c6 "shortsubject: add a subject length check" ... PASS
 * 5e74abd "*: comments and golint" ... PASS
 * 07a982f "git: add verbose output of the commands run" ... PASS
 * 03bda4b "main: add filtering of rules to run" ... PASS
 * c10ba9c "Initial commit" ... PASS

Verbosity shows each rule's output:

vbatts@valse ~/src/vb/git-validation (master) $ git-validation -v
 * d614ccf "*: run tests in a runner" ... PASS
  - PASS - has a valid DCO
  - PASS - commit subject is 72 characters or less! *yay*
 * b9413c6 "shortsubject: add a subject length check" ... PASS
  - PASS - has a valid DCO
  - PASS - commit subject is 72 characters or less! *yay*
 * 5e74abd "*: comments and golint" ... PASS
  - PASS - has a valid DCO
  - PASS - commit subject is 72 characters or less! *yay*
 * 07a982f "git: add verbose output of the commands run" ... PASS
  - PASS - has a valid DCO
  - PASS - commit subject is 72 characters or less! *yay*
 * 03bda4b "main: add filtering of rules to run" ... PASS
  - PASS - has a valid DCO
  - PASS - commit subject is 72 characters or less! *yay*
 * c10ba9c "Initial commit" ... PASS
  - PASS - has a valid DCO
  - PASS - commit subject is 72 characters or less! *yay*

Here's a failure:

vbatts@valse ~/src/vb/git-validation (master) $ git-validation 
 * 49f51a8 "README: adding install and usage" ... FAIL
  - FAIL - does not have a valid DCO
 * d614ccf "*: run tests in a runner" ... PASS
 * b9413c6 "shortsubject: add a subject length check" ... PASS
 * 5e74abd "*: comments and golint" ... PASS
 * 07a982f "git: add verbose output of the commands run" ... PASS
 * 03bda4b "main: add filtering of rules to run" ... PASS
 * c10ba9c "Initial commit" ... PASS
1 issues to fix
vbatts@valse ~/src/vb/git-validation (master) $ echo $?
1

Excluding paths that are out of the scope of your project:

vbatts@valse ~/src/vb/git-validation (master) $ GIT_CHECK_EXCLUDE="./vendor:./git/testdata" git-validation -q -run dangling-whitespace
...

using the GIT_CHECK_EXCLUDE environment variable. Multiple paths should be separated by colon(:)

Rules

Default rules are added by registering them to the validate package. Usually by putting them in their own package. See ./rules/. Feel free to contribute more.

Otherwise, by using validate package API directly, rules can be handed directly to the validate.Runner.