Commit meta data and extensions

[Dirkjan Ochtman]

On Thu, Jan 7, 2010 at 16:52, Tory Patnoe <tpatnoe at cisco.com> wrote:
> The other approach I see is to require meta-data on each commit to a given
> branch. This would involve 1 extension and 1 hook.
>
> The extension would prompt the developer at commit time to enter a task id
> and story id. That data would then be added to either the bottom of the
> commit message or to meta-data on the commit itself. I saw that commitctx's
> can have "extra" data. Is it better to put my meta-data in the commit
> message or as "extra" meta-data on the commit ctx?
>
> The hook would be on the central repository and prevent push'es without the
> necessary meta-data.

If you have structured metadata that is available at commit time, I
think putting it in extra this way would be the best solution.

Cheers,

Dirkjan