Unfortunately in this case we don't have control over the hooks at the receiving end - we want to prevent tags from being pushed by all users to these repo's.
On Wed, Apr 15, 2015 at 1:08 AM, Junio C Hamano <gits...@pobox.com> wrote: > "Chris O'Kelly" <ch...@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. > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
