You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Alexander Shorin (JIRA)" <ji...@apache.org> on 2016/03/06 12:17:46 UTC

[jira] [Commented] (INFRA-11385) Possibility of having git commit hook

    [ https://issues.apache.org/jira/browse/INFRA-11385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182111#comment-15182111 ] 

Alexander Shorin commented on INFRA-11385:
------------------------------------------

Ok, that's fine. Thank you! We'll figure something else to address this problem then.

> Possibility of having git commit hook
> -------------------------------------
>
>                 Key: INFRA-11385
>                 URL: https://issues.apache.org/jira/browse/INFRA-11385
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: Git
>            Reporter: Alexander Shorin
>            Assignee: Daniel Gruno
>
> Hi!
> This is not a wish yet, but mostly a question about possibility of adding git commit hook on apache/couchdb repository.
> Long story short:
> In apache/couchdb repo we have [rebar.config.script|https://github.com/apache/couchdb/blob/master/rebar.config.script#L25-L61] file where we pin commit hash / git tag for each subapp we use. It's easy to make a mistake and commit something wrong there, so the idea is to have some git commit hook on this file that will ensure that specified commit hashes / tags are exists, valid and could be used, otherwise - reject.
> So two questions there:
> 1. Is it possible to have own custom git commit hook?
> 2. And if it is, what do we need to do (in addition to write the code) to make it work?
> P.S. Yes, the simple workaround is to do PR first, check how it goes on CI and commit when it's green, but we cannot fix "optional" nature of this workflow - everyone can easily bypass it. Executive decree vs technical containment problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)