Re: [Opinion gathering] Git remote whitelist/blacklist
- From
Lars Schneider <larsxschneider@gmail.com>
- Date
- May 24, 2016, 19:11 UTC
- Message-ID
- <B559ECA4-0C95-4E40-8E2C-22299614E559@gmail.com>
- In-Reply-To
- <CAPc5daURo8SkbeGf0MEsp0sLzdzFfUOxptgusFr58UG9SKmDAA@mail.gmail.com>
Show 15 quoted lines
> On 24 May 2016, at 12:07, Junio C Hamano <gitster@pobox.com> wrote: > > On Tue, May 24, 2016 at 5:55 AM, Matthieu Moy > <Matthieu.Moy@grenoble-inp.fr> wrote: >> So, when trying a forbidden push, Git would deny it and the only way to >> force the push would be to remove the blacklist from the config, right? >> >> Probably the sanest way to go. I thought about adding a "git push >> --force-even-if-in-blacklist" or so, but I don't think the feature >> deserves one specific option (hence add some noise in `git push -h`). > > Yeah, I agree --even-if-in-blacklist is a road to madness, but I wonder > how this is different from setting pushURL to /dev/null or something > illegal and replace that phony configuration value when you really need > to push?
It is no different from changing the push URL. As a matter of fact, that is how I've implemented this "blacklist" feature with the current version of Git: https://speakerdeck.com/larsxschneider/git-at-scale?slide=35
- Lars