-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TECH: add git hooks #443
TECH: add git hooks #443
Conversation
5b9a9c9
to
dd12afd
Compare
dd12afd
to
0d3560a
Compare
aeed35a
to
d90255a
Compare
|
||
gitMessageFile="$1" | ||
gitMessage=$(cat $gitMessageFile) | ||
gitMessagePattern="^(Revert \")?(ISSUE-\d+|TECH):\s\w+.*" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is an ISSUE or TECH? 2 types of tasks will be enough for us?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I see on the board we use issues for anything, for features, for bugs and so on. If you are doing some small fix and don't want to create a dedicated issue for it, you can simply use TECH. So I guess it is enough.
No description provided.