Re: Feature Request: provide cmdline args to git hooks

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 14, 2015, 15:08 UTC
Message-ID: <xmqqwq1e3fy4.fsf@gitster.dls.corp.google.com>
In-Reply-To: <CAM-hpQcgOgrAJBAZrH4icDtJMiHUYOz1tynYkoj7qzyVMZ0eVQ@mail.gmail.com>

"Chris O'Kelly" <chris@mapcreative.com.au> writes:

Show 8 quoted lines

> 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.