Closed Ostrzy closed 10 years ago
[noreview] in commit description is probably more canonical
More canonical with what?
@sheerun are there any conventions regarding commit messages? I mean, not our guidelines, but git world in general.
http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html + Travis CI and other tools use [flags] in square brackets in commit description, to not pollute git history.
Travis checks for [ci skip]
or [skip ci]
, so I propose [review skip]
or something similar. #noreview
sucks balls, because you have to find a workaround in order to put it as the first in a new line (such flags should never appear in the first line of commit message—neither should fixes #1
etc.)
[skip review], [ci skip] is backwards https://github.com/travis-ci/travis-ci/issues/911
/\[(skip.*review)|(review.*skip)\]/
This one we are using now. Not catching only backward one.
/#?(no|skip)\s?(code\s?)?review/
I think "#" or "[ ]" should be mandatory to prevent false positives.
Agreed with @teamon.
@teamon argument is fine with me. So I guess decision is to use "[]"?
/\[\s*(no|skip)\s+(code\s*)?review\s*\]/ + reverse
:+1:
@teamon Reverse You say? [review code no]?
[(no|skip) (code) review] or [review (no|skip)]
who the hell is going to write [skip code review] instead of [skip review]
@teamon The first one is quite natural, but when I read the second one, I feel like I should have lightsabre. I'm opting for no reverse. @sheerun I have no idea :grinning:
The reverse started with [ci skip] but I'm fine with "just" [(no|skip) review] and nothing more.
:+1: for [(no|skip) review]
@Ostrzy PR plz
@Ostrzy
@Ostrzy !
Examples of such commits: