From: "Stuart P. Bentley" <stuart@testtrack4.com>
To: git@vger.kernel.org
Subject: Feature request: Specify hooks on the command line
Date: Thu, 17 Jul 2014 16:54:41 -0700 [thread overview]
Message-ID: <lq9no7$675$1@ger.gmane.org> (raw)
I'm developing a project called [Plushu][], an ecosystem for creating
plugin-based dedicated user shells, patterned after [Dokku][] (and
similar to git-shell).
[Plushu]: https://github.com/plushu/plushu
[Dokku]: https://github.com/progrium/dokku
Plushu has its own hook system for plugins (so multiple plugins can
listen on a single hook). Right now, to extend Git's hooks to Plushu's
plugins, Plushu's plugin for Git links the "$GIT_DIR/hooks" directory
for all new repositories to a directory with scripts that delegate to
Plushu's hook system.
I'd rather not have to alter the repository directories to create this
interface, so it would be a significant improvement if Git provided some
mechanism to specify hooks on the command line. I was thinking something
like a GIT_HOOKS_DIR environment variable, or perhaps a "--hooks
update=/opt/hook"-style option.
(Perhaps, as a more general solution, there should be a way of
specifying alternatives for individual GIT_DIR subdirectories per-command?)
I'm willing to draft the patch for this if someone could point me to the
relevant spot(s) in the code.
reply other threads:[~2014-07-18 0:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='lq9no7$675$1@ger.gmane.org' \
--to=stuart@testtrack4.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.
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 NNTP newsgroup(s).