[
https://issues.apache.org/jira/browse/AVRO-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15276529#comment-15276529
]
Ryan Blue commented on AVRO-1841:
---------------------------------
I'm just pointing out another way I've seen it done, I don't have a strong
opinion on how to do this. The commit hook sounds like a reasonable way to go,
but I'm not sure many people would use it since commit hooks in git are
self-enforced.
> Automatically verify the commit messages
> -----------------------------------------
>
> Key: AVRO-1841
> URL: https://issues.apache.org/jira/browse/AVRO-1841
> Project: Avro
> Issue Type: Improvement
> Components: build
> Reporter: Niels Basjes
> Assignee: Niels Basjes
> Fix For: 1.8.1
>
> Attachments: AVRO-1841-20160507.patch
>
>
> Last week I made a commit and I made an error: The commit message was not
> fully according to the right format.
> To avoid future mistakes I propose we introduce validation to the commit
> message by using the git hooks.
> These can be run in two places: client side and server side.
> This ticket focuses on the client side hooks. If we decide to add this also
> to the server side that must be a separate ticket.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
