Git development
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jeff King <peff@peff.net>
Cc: Scott Chacon <schacon@gmail.com>, git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] add a 'pre-push' hook
Date: Tue, 19 Aug 2008 12:59:28 -0700	[thread overview]
Message-ID: <20080819195928.GB24212@spearce.org> (raw)
In-Reply-To: <20080819190832.GC17943@coredump.intra.peff.net>

Jeff King <peff@peff.net> wrote:
> I think the common wisdom has been that such tests should be done on the
> _receiving_ end, since that makes a more trustworthy enforcement point.
> E.g., I know that crap can't get into my central repo because a hook
> checks everything coming in. But if a developer has turned off his
> pre-push hook (or accidentally failed to enable it), he can still send
> crap.
> 
> One other argument I have seen is that, to prevent the proliferation of
> hooks, the rule is not to add a hook that could just as easily be done
> as a sequence of commands. IOW, what's wrong with
> 
>   run_my_automated_tests && git push

Yup, I agree completely.

Why not just setup an alias:

	git config alias.send '! run_my_tests && git push "$@"'

and retrain your fingers to use "git send ..."?
 
-- 
Shawn.

  reply	other threads:[~2008-08-19 20:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1219170876-46893-1-git-send-email-schacon@gmail.com>
2008-08-19 18:55 ` [PATCH] add a 'pre-push' hook Scott Chacon
2008-08-19 18:58   ` Jeff King
2008-08-19 19:00     ` Scott Chacon
2008-08-19 19:08       ` Jeff King
2008-08-19 19:59         ` Shawn O. Pearce [this message]
2008-08-19 20:26           ` Scott Chacon
2008-08-19 21:26             ` しらいしななこ
2008-08-19 21:45               ` Scott Chacon
2008-08-19 22:23                 ` Junio C Hamano
2008-08-19 22:26         ` Sam Vilain
2008-08-20  0:15           ` Jeff King
2008-08-19 19:39       ` Junio C Hamano
2008-08-19 19:58         ` Scott Chacon
2008-08-19 23:35           ` Junio C Hamano
2008-08-19 23:39             ` Shawn O. Pearce

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=20080819195928.GB24212@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=schacon@gmail.com \
    /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