Skip to content
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

Merged
merged 2 commits into from
Dec 5, 2022
Merged

TECH: add git hooks #443

merged 2 commits into from
Dec 5, 2022

Conversation

eakurnikov
Copy link
Collaborator

No description provided.

build.gradle.kts Outdated Show resolved Hide resolved
build.gradle.kts Outdated Show resolved Hide resolved
.githooks/pre-commit Outdated Show resolved Hide resolved
.githooks/commit-msg Outdated Show resolved Hide resolved

gitMessageFile="$1"
gitMessage=$(cat $gitMessageFile)
gitMessagePattern="^(Revert \")?(ISSUE-\d+|TECH):\s\w+.*"
Copy link
Collaborator

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?

Copy link
Collaborator Author

@eakurnikov eakurnikov Dec 5, 2022

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.

@eakurnikov eakurnikov merged commit f5414db into master Dec 5, 2022
AzamatCherchesov added a commit that referenced this pull request Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants