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

Robert Muir commented on LUCENE-5383:
-------------------------------------

{quote}
I would suggest a convention of "github pull req #xxx" may help clarify longer 
term.
{quote}

I don't think we should make this complicated without good reason. We should 
use consistent naming in CHANGES.txt and in commit messages like we do today, 
and it should also be recognized by github so the contributor knows we actually 
committed the thing.



> fix changes2html to link pull requests
> --------------------------------------
>
>                 Key: LUCENE-5383
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5383
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Robert Muir
>
> If someone submits a pull request, i think we should put it in changes.txt in 
> some way similar to the jira issues:
> e.g. for a JIRA issue we do:
> {noformat}
> * LUCENE-XXXX: Add FooBar.  (Joe Contributor via John Committer)
> {noformat}
> changes2html recognizes and expands these to jira issue links.
> so I think we should be able to do something like:
> {noformat}
> * pull request #xxx: Add FooBar. (Joe Contributor via John Committer)
> {noformat}
> and have it link to the request, too.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to