git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gisle Aas <gisle@aas.no>
To: git@vger.kernel.org
Subject: Make author and committer available to pre-commit hook
Date: Mon, 5 Jul 2010 13:30:46 +0200	[thread overview]
Message-ID: <AANLkTinpCDRf_Yhuj2-tdZwmvHk8yna1Xjdtbrmx35CB@mail.gmail.com> (raw)

I would like to implement a pre-commit hook that validates the
--author set for the commit.  Our use case is a shared repository of
configuration info where different persons all commit as root; but we
want to make sure they override the --author to something sensible.

What would be the preferred mechanism to pass on this information?  It
could for instance be arguments to the hook script or via environment
variables.

I created the following patch to explore what it would take to pass on
this information as command line arguments.  It seems to do the trick
for me.  Any drawback with this approach?

Regards,
Gisle


diff --git a/builtin/commit.c b/builtin/commit.c
index c101f00..acb8dc2 100644
--- a/builtin/commit.c
+++ b/builtin/commit.c
@@ -557,8 +557,20 @@ static int prepare_to_commit(const char
*index_file, const char *prefix,
        const char *hook_arg2 = NULL;
        int ident_shown = 0;

-       if (!no_verify && run_hook(index_file, "pre-commit", NULL))
+       determine_author_info();
+       if (!no_verify) {
+           int rc;
+           hook_arg1 = xstrdup(fmt_name(author_name, author_email));
+           hook_arg2 = xstrdup(fmt_name(getenv("GIT_COMMITTER_NAME"),
+                                        getenv("GIT_COMMITTER_EMAIL")));
+           rc = run_hook(index_file, "pre-commit", hook_arg1, hook_arg2, NULL);
+           free((char*)hook_arg1);
+           free((char*)hook_arg2);
+           if (rc)
                return 0;
+           hook_arg1 = NULL;
+           hook_arg2 = NULL;
+       }

        if (message.len) {
                strbuf_addbuf(&sb, &message);
@@ -632,8 +644,6 @@ static int prepare_to_commit(const char
*index_file, const char *prefix,

        strbuf_release(&sb);

-       determine_author_info();
-
        /* This checks if committer ident is explicitly given */
        git_committer_info(0);
        if (use_editor && include_status) {

             reply	other threads:[~2010-07-05 11:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 11:30 Gisle Aas [this message]
2010-07-05 11:46 ` Make author and committer available to pre-commit hook Jeff King
2010-07-05 18:04   ` Gisle Aas
2010-07-05 21:31     ` Ævar Arnfjörð Bjarmason
2010-07-06  3:04       ` Junio C Hamano
2010-07-06  7:29         ` Jeff King
2010-07-06  9:22           ` Gisle Aas
2010-07-06 15:47             ` Junio C Hamano

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=AANLkTinpCDRf_Yhuj2-tdZwmvHk8yna1Xjdtbrmx35CB@mail.gmail.com \
    --to=gisle@aas.no \
    --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).