From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Moss, Adam David" <admoss1980@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Annotated Tag Hooks?
Date: Mon, 14 Nov 2022 22:45:43 +0000 [thread overview]
Message-ID: <Y3LFF9EFVlCn4Lt2@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <CAMTDv-8kxu-vwtCgz-VGBhYEbUX8edXzyaQK4szg2bmMJLjF4g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
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.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2022-11-14 22:46 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 [this message]
2022-11-14 22:51 ` Taylor Blau
2022-11-14 23:04 ` rsbecker
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y3LFF9EFVlCn4Lt2@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=admoss1980@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://80x24.org/mirrors/git.git
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).