[ckan-dev] Trac ticket refs in commit messages

Aron Carroll aron.carroll at okfn.org
Fri Jun 1 11:22:39 UTC 2012


I'm generally for this as I think the ticket reads better, but if
keeping the ticket number at the start helps Adrià out then I'm good
with that too.

Cheers,
Aron

On 31 May 2012, at 20:54, Adrià Mercader wrote:

> On one hand I perhaps prefer having all ticket numbers at the start of
> the commit message, but I think the ability to close or refer to trac
> tickets is really cool, so I'm happy if everyone else is.
> Also if all devs update the changelog it will be less important to go
> through the commit list on each release
> 
> 
> Adrià
> 
> On 31 May 2012 18:57, Sean Hammond <sean.hammond at okfn.org> wrote:
>> Speaking to Adria especially, what do you think of this commit message
>> stuff I added to the coding standards?
>> 
>> http://docs.ckan.org/en/latest/coding-standards.html
>> 
>> It changes the syntax for referring to trac tickets from the [#123] at
>> the start of the first line to stuff like "closes #123", "see #123" etc.
>> anywhere in the commit message. It's the syntax used by the github-trac
>> plugin. Not tested yet as I won't install the plugin until trac is
>> updated
>> 
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-dev
> 
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev





More information about the ckan-dev mailing list