Letting remote repositories override local configuration
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Mar 19, 2012, 09:35 UTC
- Message-ID
- <20120319093505.GA10017@burratino>
- In-Reply-To
- <alpine.DEB.2.00.1203190945560.15290@ds9.cixit.se>
Peter Krefting wrote:
Show 6 quoted lines
> I know the policy in Git is to not allow the remote repository > dictate anything about the configuration in the local repository, > but as an alternative to changing the "push.default" value, perhaps > we should allow setting some configuration option on the remote > repository that blocks it from being the target of a "push.default = > matching" push?
If I work for your company and always keep all my local topic branches in good order, I would expect to be permitted to use "push.default = matching" to easily push them all at once after I have finished preparing them, provided I have set up my local copy of git that way explicitly, regardless of what the person setting up the infrastructure thought.
What would I be missing?
Curious, Jonathan