From: Junio C Hamano <gitster@pobox.com>
To: "Chris O'Kelly" <chris@mapcreative.com.au>
Cc: git@vger.kernel.org
Subject: Re: Feature Request: provide cmdline args to git hooks
Date: Tue, 14 Apr 2015 08:08:51 -0700 [thread overview]
Message-ID: <xmqqwq1e3fy4.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAM-hpQcgOgrAJBAZrH4icDtJMiHUYOz1tynYkoj7qzyVMZ0eVQ@mail.gmail.com> (Chris O'Kelly's message of "Tue, 14 Apr 2015 13:42:45 +1000")
"Chris O'Kelly" <chris@mapcreative.com.au> writes:
> A brief background of my use case:
> I am wanting to write a pre-push hook to prevent tags being pushed to
> our production servers. The production servers in our case are --bare
> endpoints, and when we push a tag at them, they always checkout the
> commit that tag is attached to via some post-receive magic (WPEngine,
> FWIW). This behavior is even present when the tag was already pushed
> to the repo previously, if for instance a normal push is made with the
> --tags argument.
Do you mean that you want to forbid some people from pushing tags
into that repository while allowing others (i.e. those who manage
production deployment)? If that is the goal, it sounds like that
the right place to do this is at the receiving end via pre-receive,
not at the sending end via pre-push.
next prev parent reply other threads:[~2015-04-14 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 3:42 Feature Request: provide cmdline args to git hooks Chris O'Kelly
2015-04-14 15:08 ` Junio C Hamano [this message]
2015-04-14 22:28 ` Chris O'Kelly
2015-04-14 23:46 ` Junio C Hamano
2015-04-15 0:21 ` Chris O'Kelly
2015-04-15 18:18 ` 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=xmqqwq1e3fy4.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=chris@mapcreative.com.au \
--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