You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2011/03/13 12:04:59 UTC

[jira] Updated: (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:all-tabpanel ]

Robbie Gemmell updated INFRA-3493:
----------------------------------

    Attachment: issue_ref_check.sh
                issue_ref_check.config

A first cut at a reference checking script. I was going to add some error handling to it before putting it up, but just doing it now in light of most recent comments.

> 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
>         Attachments: issue_ref_check.config, issue_ref_check.sh
>
>
> 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