Re: Git and Scmbug integration

From: David Symonds <dsymonds@gmail.com>
Date: Nov 14, 2007, 00:02 UTC
Message-ID: <ee77f5c20711131602m5b9042fx72689af53e24ddd2@mail.gmail.com>
In-Reply-To: <1194998142.4106.24.camel@localhost>

On Nov 14, 2007 10:55 AM, Kristis Makris <kristis.makris@asu.edu> wrote:

Show 9 quoted lines

> On Wed, 2007-11-14 at 10:00 +1100, David Symonds wrote:
> > > 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.
>
> Even if that is true, there no hook that will trigger when a local tag
> is applied.

Unannotated tags don't make a proper new object, only a ref. If you stick to annotated tags, you'll get new objects added which, I think, should trigger the post-commit hook.

> I'd like the commit hook to provide enough information to be able to
> tell which files were modified and their respective old/new version (or
> perhaps their old/new SHA-1 hash). If the new SHA-1 hash can be used to
> extract all that, that's ok with me. But right now there's nothing.

If you have the new commit's SHA-1, it's very simple to get the parent commit's SHA-1 and do whatever you want. A complexity would be with handling merges, where a commit has multiple parents. If you have a commit SHA-1 hash, you can just "git diff --name-only <hash>^ <hash>" to get a list of the files changed by <hash>.

Dave.