On Nov 14, 2007 6:06 AM, Kristis Makris <kristis.makris@xxxxxxx> wrote: > Hello, > > I've been working on adding Git support in Scmbug, a system that > integrates software configuration management with bug-tracking. I've run > across what seem to be limitations in the Git hooks mechanism (at least > in version 1.5.1.3). In particular: > > > (1) > > http://bugzilla.mkgnu.net/show_bug.cgi?id=991 > > There's no hook that will trigger when a tag is applied. I believe the 'update' hook is run when the tag is pushed. > (2) > > http://bugzilla.mkgnu.net/show_bug.cgi?id=992 > > Git does not offer metadata describing a change on the commit trigger > > The commit trigger seems to be "post-commit" but it supplies no arguments. The > "update" trigger supplies a lot of information but that's only triggered when > changes are published to a remote repository. Isn't this some kind of centralised bug-tracking system anyway? It would be nice, I see, for the 'commit' hook to take, say, the commit SHA-1 hash as a parameter. Dave. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
