Git and tagging hook

Hello,

It seems that Git (at least v1.5.6) does not offer hooks on tag creation
(a pre-tag and a post-tag hook). I need such a hook for integrating tag
activities with an issue-tracker. Is it possible to add this hook ?

I had asked about this in the past, but did not receive a response.

http://bugzilla.mkgnu.net/show_bug.cgi?id=991

Thanks,
Kristis

Kristis Makris wrote:

Hello,

It seems that Git (at least v1.5.6) does not offer hooks on tag creation
(a pre-tag and a post-tag hook). I need such a hook for integrating tag
activities with an issue-tracker. Is it possible to add this hook ?

What you want is probably the post-receive or 'update' hooks on whatever
repository you consider your public watering hole for your project.
Integrating with an issue-tracker from the developers machine would be
utterly stupid, as it would prevent tagging from happening while not
connected.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Next time, don't include a members-only list in the CC, please. The
usual action when replying to an email on git@vger is to "Reply All",
which doesn't play nicely with such lists and will render one list
archive incomplete (since people will inevitably cull that other
list from their CC's after having sent to it once).

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

But the post-receive is NOT executed when I apply a tag.

I want the integration when I apply the tag to a local repository, NOT
only when I push/pull.

On Mon, 2008-10-06 at 09:17 +0200, Andreas Ericsson wrote:

Kristis Makris wrote:

quoted

Hello,

It seems that Git (at least v1.5.6) does not offer hooks on tag creation
(a pre-tag and a post-tag hook). I need such a hook for integrating tag
activities with an issue-tracker. Is it possible to add this hook ?

What you want is probably the post-receive or 'update' hooks on whatever
repository you consider your public watering hole for your project.
Integrating with an issue-tracker from the developers machine would be
utterly stupid, as it would prevent tagging from happening while not
connected.

Kristis Makris wrote:

But the post-receive is NOT executed when I apply a tag.

I want the integration when I apply the tag to a local repository, NOT
only when I push/pull.

If you are talking about taging locally, you can simply make an alias
or do something after tagging. Search archives for description when
it is worth to add a hook, and when it is not.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

On Mon, 2008-10-06 at 09:20 +0200, Andreas Ericsson wrote:

Next time, don't include a members-only list in the CC, please. The
usual action when replying to an email on git@vger is to "Reply All",
which doesn't play nicely with such lists and will render one list
archive incomplete (since people will inevitably cull that other
list from their CC's after having sent to it once).

Why would they cull that other list, if the usual action is to "Reply
All" ?

Kristis Makris wrote:

On Mon, 2008-10-06 at 09:20 +0200, Andreas Ericsson wrote:

quoted

Next time, don't include a members-only list in the CC, please. The
usual action when replying to an email on git@vger is to "Reply All",
which doesn't play nicely with such lists and will render one list
archive incomplete (since people will inevitably cull that other
list from their CC's after having sent to it once).

Why would they cull that other list, if the usual action is to "Reply
All" ?

Because it's a members-only list. Like me, I'm sure many will get
annoyed enough to remember to remove it for further postings on the
subject. Those nonsensical "awaiting moderator approval" emails are
irritating noise, and since they're "To: me" and get a low spamrank
they go straight to the high-priority folder. Many others on this
list use similar filters as it's a neat way of dealing with several
high-volume mailing lists sanely.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

On Tue, 2008-10-07 at 19:28 +0200, Jakub Narebski wrote:

Kristis Makris wrote:

quoted

But the post-receive is NOT executed when I apply a tag.

I want the integration when I apply the tag to a local repository, NOT
only when I push/pull.

If you are talking about taging locally, you can simply make an alias
or do something after tagging. Search archives for description when
it is worth to add a hook, and when it is not.

I am looking for a guarantee that is better than casually saying
"simply". I will be providing the integration work to users that may not
be as comfortable with making aliases. 

I still don't see why a hook on local tagging is not available. Is it
possible to add support in Git for such a hook ? Both pre-tag and
post-tag.

Kristis Makris wrote:

On Tue, 2008-10-07 at 19:28 +0200, Jakub Narebski wrote:

quoted

Kristis Makris wrote:

quoted

But the post-receive is NOT executed when I apply a tag.

I want the integration when I apply the tag to a local repository, NOT
only when I push/pull.

If you are talking about taging locally, you can simply make an alias
or do something after tagging. Search archives for description when
it is worth to add a hook, and when it is not.

I am looking for a guarantee that is better than casually saying
"simply". I will be providing the integration work to users that may not
be as comfortable with making aliases. 

I still don't see why a hook on local tagging is not available. Is it
possible to add support in Git for such a hook ? Both pre-tag and
post-tag.

Because noone's ever needed one before. If aliases can't do what you
want, write a patch to support it and hope Junio accepts it. It's really
quite straight-forward. Make sure you read Documentation/SubmittingPatches
before you send it.

Note though that use of tags on the developer's side will still be up
to the developer and not something you can force through other means
than policy or convention.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

On Wed, Oct 08, 2008 at 19:40:02 +0200, Andreas Ericsson wrote:

Kristis Makris wrote:

quoted

On Tue, 2008-10-07 at 19:28 +0200, Jakub Narebski wrote:

quoted

Kristis Makris wrote:

quoted

I want the integration when I apply the tag to a local repository, NOT
only when I push/pull.

Care to explain why that would ever be useful? It's local, which means that:
 - the user can take it back without a trace it ever happened (git tag -d or
   even git update-ref -d) and
 - noone except the user will see it anyway, so it's not like they should
   care either.

Besides, you don't need git tag to create a tag in git, so the hook wouldn't
really be guaranteed anyway (I mean, just like the commit hook is not -- you
can still commit by calling write-tree, commit-tree and update-ref and avoid
the hook).

quoted

quoted

If you are talking about taging locally, you can simply make an alias
or do something after tagging. Search archives for description when
it is worth to add a hook, and when it is not.

I am looking for a guarantee that is better than casually saying
"simply". I will be providing the integration work to users that may not
be as comfortable with making aliases. 

I still don't see why a hook on local tagging is not available. Is it
possible to add support in Git for such a hook ? Both pre-tag and
post-tag.

Because noone's ever needed one before. If aliases can't do what you
want, write a patch to support it and hope Junio accepts it. It's really
quite straight-forward. Make sure you read Documentation/SubmittingPatches
before you send it.

Note though that use of tags on the developer's side will still be up
to the developer and not something you can force through other means
than policy or convention.

Being possible was never a reason to add features to git and the less it was
a reason to add hooks. And there does not seem to be a use-case that would
clearly benefit from having such hooks, or at least none was shown on the
list so far.

For integration with issue tracker, the local tag is neither final, nor
useful to anybody except the user who did it until it hits the central
repository. And working on the central repository directly does not seem like
a good idea either.

-- 
						 Jan 'Bulb' Hudec [off-list ref]