You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Tony Stevenson (JIRA)" <ji...@apache.org> on 2011/03/07 15:57:59 UTC
[jira] Commented: (INFRA-3493) JIRA reference pre-commit hook for
Apache Qpid
[ https://issues.apache.org/jira/browse/INFRA-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003375#comment-13003375 ]
Tony Stevenson commented on INFRA-3493:
---------------------------------------
Robbie,
We are very unlikely to implement such a hook. As implementing this in and adhoc fashion across all projects could be an expensive operation.
We already have a pre-commit hook we use globally. If however you write a script, we might consider it's implementation. It would need to be efficient and effective.
You will need to use svnlook to determine if the commit is in the correct path.
> JIRA reference pre-commit hook for Apache Qpid
> ----------------------------------------------
>
> Key: INFRA-3493
> URL: https://issues.apache.org/jira/browse/INFRA-3493
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Robbie Gemmell
> Priority: Minor
>
> The Apache Qpid project would like to have a Subversion pre-commit hook added to enforce that commit log messages for the project contain either a JIRA issue reference (eg QPID-1234) or alternatively include NO-JIRA to escape enforcement of the commit hook. If neither is found, the commit would fail and alert the committer to either include an issue reference or use NO-JIRA to escape the script.
> 1) Can we have such a commit hook?
> 2) If so, would you implement it or would we need to provide an appropriate script?
> Thanks,
> Robbie
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira