mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: <>
To: "'Taylor Blau'" <>,
	"'brian m. carlson'" <>,
	"'Moss, Adam David'" <>,
Subject: RE: Annotated Tag Hooks?
Date: Mon, 14 Nov 2022 18:04:43 -0500	[thread overview]
Message-ID: <013601d8f87d$7edc0ae0$7c9420a0$> (raw)
In-Reply-To: <Y3LGYvgEsqPsAo0F@nand.local>

On November 14, 2022 5:51 PM, Taylor Blau wrote:
>On Mon, Nov 14, 2022 at 10:45:43PM +0000, brian m. carlson wrote:
>> On 2022-11-12 at 11:10:38, Moss, Adam David wrote:
>> > Hello,
>> >
>> > Is there any way to use, or are there any plans to introduce, an
>> > equivalent of the `prepare-commit-msg`, `commit-msg`, and
>> > `post-commit` hooks but for `git tag` events?
>> >
>> > I would like to make use of `git interpet-trailers` to automate the
>> > inclusion of some additional information into the tag annotation in
>> > the same way we do with commit messages, but am struggling to come
>> > up with a nice solution at the moment.
>> >
>> > If there is a better approach I could use I'd welcome suggestions?
>> > Alternatively I'd be willing to help implement such a capability if
>> > anyone would be willing to mentor me through it?
>> Without speaking for anyone else, I think such a feature would be
>> beneficial and I'd be happy to see it come in.  I'm not personally
>> able to mentor you on this, because I have limited time to work on
>> Git, but perhaps someone else on the list would come along and be
>> happy to walk you through it.
>> I _would_ be fine with being put on a CC for the patches to provide a
>> review, however.
>Ditto for both ;-).

This feature is of interest to my community as well. Please CC me also.

      reply	other threads:[~2022-11-14 23:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-12 11:10 Annotated Tag Hooks? Moss, Adam David
2022-11-14 22:45 ` brian m. carlson
2022-11-14 22:51   ` Taylor Blau
2022-11-14 23:04     ` rsbecker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='013601d8f87d$7edc0ae0$7c9420a0$' \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).