From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: RFE: default hooks for git repositories
Date: Fri, 5 Apr 2019 13:43:29 -0400 [thread overview]
Message-ID: <20190405174329.GA21472@chatter.qube.local> (raw)
In-Reply-To: <20190401180403.o4zgowgyh3qq23iz@dcvr>
On Mon, Apr 01, 2019 at 06:04:03PM +0000, Eric Wong wrote:
>> Sorry, Eric, I'm close to declaring email bankruptcy. :) I am okay
>> with any
>> solution that lets us add hooks. To explain why we need hooks in
>> public-inbox repos, it's mostly for the ease of mirroring -- I want a
>> post-update hook to update the grokmirror [1] manifest so that our mirroring
>> script knows when there are updates and also when there are new archives or
>> repository epochs added.
>>
>> So, I defer to you entirely when it comes to how to do it. :)
>
>Yes, putting the hook in the init.templateDir should get you
>what you want. It would work the same for newly-created code
>repositories, too.
So, I just realized that, at least when mail is delivered via
public-inbox-mda, none of the hooks are ever triggered. I've tried with
post-update, post-receive, post-commit, pre-commit, etc. Am I doing
something wrong, or is this because the operation is being done on a low
enough level that the hooks aren't triggered as they would with a
regular git operation?
-K
next prev parent reply other threads:[~2019-04-05 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 17:03 RFE: default hooks for git repositories Konstantin Ryabitsev
2019-03-07 2:42 ` Eric Wong
2019-03-08 23:01 ` Eric Wong
2019-03-18 23:11 ` Eric Wong
2019-04-01 15:41 ` Konstantin Ryabitsev
2019-04-01 18:04 ` Eric Wong
2019-04-05 17:43 ` Konstantin Ryabitsev [this message]
2019-04-05 20:07 ` Eric Wong
2019-04-06 4:52 ` Eric Wong
2019-04-15 18:29 ` [PATCH] TODO: add an item for hooks support Eric Wong
2019-04-29 0:33 ` update on grokmirror integration [was: [PATCH] TODO: add an item for hooks support] Eric Wong
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: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190405174329.GA21472@chatter.qube.local \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--cc=meta@public-inbox.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.
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).