[ckan-dev] Trac ticket refs in commit messages

Aron Carroll aron.carroll at okfn.org
Wed Jun 6 09:06:54 UTC 2012


> Hmm, yeah. We could just avoid saying
> close/closed/closes/fix/fixed/fixes #123 and only use
> references/refs/ref/addresses/re/see #123

I'm fine with not using the close shortcuts. If this plugin works the same way as GitHub issues it should pick up [#123] in which case I think that's probably the cleanest way forward.

> If the github-trac plugin will automatically make our commit messages
> appear as comments on the trac ticket if we reference the ticket number,
> I can see that being useful.

I assume thats what it does, otherwise as you say it's pretty useless :) I guess we install it and give it a go.

On 6 Jun 2012, at 10:03, Sean Hammond wrote:

>>> Maybe we have to settle for letting trac tickets get closed before stuff
>>> has been merged into master?
>>> 
>> 
>> I'd rather close the ticket manually than get it closed automatically
>> before it's been reviewed and merged.
> 
> Hmm, yeah. We could just avoid saying
> close/closed/closes/fix/fixed/fixes #123 and only use
> references/refs/ref/addresses/re/see #123, or I could disable the
> github-trac plugin's automatic ticket closing by hacking the source
> code. If we're gonna make our own fork of this plugin we could also make
> it recognise our [#123] syntax if we wanted.
> 
> If the github-trac plugin will automatically make our commit messages
> appear as comments on the trac ticket if we reference the ticket number,
> I can see that being useful. Otherwise maybe we don't actually want this
> plugin at all. I'll have to test the plugin to see if it even does this,
> which I'll do once trac has been updated.
> 
> _______________________________________________
> 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