Re: Git and Scmbug integration
- From
David Symonds <dsymonds@gmail.com>
- Date
- Nov 14, 2007, 00:27 UTC
- Message-ID
- <ee77f5c20711131627q329d45aepe48102728cf2778c@mail.gmail.com>
- In-Reply-To
- <1194999404.4106.40.camel@localhost>
On Nov 14, 2007 11:16 AM, Kristis Makris <kristis.makris@asu.edu> wrote:
Show 13 quoted lines
> > 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 ?
Okay, I don't know about that. Someone else might want to weigh in on this.
Show 11 quoted lines
> > 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 ?
Sure -- I've got a patch for it that I'll send shortly. It's using the existing shell git-commit, so might be suitable for maint; I haven't followed what's happened with the builtinification of git-commit.
Dave.