Thread (15 messages) flat view 15 messages, 8 authors, 2016-06-15

Re: git push default behaviour?

From: Jeremy Morton <hidden>
Date: 2016-06-15 22:53:18

Would that deny non fast-forwards for all branches, though, or just
selected ones?  We'd like to just to it for 2 of our branches.  We'd
also like to explitly ALLOW fast-forwards to master, when we want to
merge in from develop to master.

A better description of what we want is to prevent 'rewriting of
history' for some of our branches.

Best regards,
Jeremy Morton (Jez)

On Tue, Mar 13, 2012 at 4:27 PM, Jakub Narebski [off-list ref] wrote:
On Thu, 8 Mar 2012, Jeremy Morton wrote:
quoted
On Thu, Mar 8, 2012 at 11:33 AM, Jakub Narebski [off-list ref] wrote:
quoted
quoted
You can always configure server to refuse forced pushes.
We're using github, and as far as I'm aware, there's no way to
configure github to do that.
It would be nice if GitHub supported setting receive.denyNonFastForward
and receive.denyDeletes (the receive.*current* do not matter for GitHub).
Though I am not sure if it would not require changes to the custom Git
implementation they use...

--
Jakub Narebski
Poland
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help