git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git and Scmbug integration

From
KMKristis Makris <kristis.makris@asu.edu>
Date
Nov 14, 2007, 00:16 UTC
Message-ID
<1194999404.4106.40.camel@localhost>
In-Reply-To
<ee77f5c20711131602m5b9042fx72689af53e24ddd2@mail.gmail.com>
On Wed, 2007-11-14 at 11:02 +1100, David Symonds wrote:
Show 14 quoted lines
> On Nov 14, 2007 10:55 AM, Kristis Makris <kristis.makris@asu.edu> wrote:
> > 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 just tried again tagging with both:
$ git tag TAG_NAME
$ git tag -a TAG_NAME
and I don't get the post-commit hook executed.
Perhaps I missed something ?
Show 10 quoted lines
> > 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>.

This sounds great. If the post-commit hook could now provide the new commit SHA-1 hash than that should be what I need.

Can the new commit SHA-1 hash be added as a parameter to the post-commit hook please ?

Previous: David SymondsNext: David Symonds
Message 5 of 17 in “Git and Scmbug integration”
  1. Kristis MakrisNov 13, 2007
  2. David SymondsNov 13, 2007
  3. Kristis MakrisNov 13, 2007
  4. David SymondsNov 14, 2007
  5. Kristis MakrisNov 14, 2007
  6. David SymondsNov 14, 2007
  7. Junio C HamanoNov 14, 2007
  8. David SymondsNov 14, 2007
  9. Junio C HamanoNov 14, 2007
  10. Junio C HamanoNov 14, 2007
  11. Martin LanghoffNov 14, 2007
  12. Alex RiesenNov 13, 2007
  13. David SymondsNov 13, 2007
  14. Alex RiesenNov 14, 2007
  15. David SymondsNov 14, 2007
  16. Kristis MakrisNov 14, 2007
  17. Kristis MakrisAug 13, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.