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 <jnareb@xxxxxxxxx> wrote: > On Thu, 8 Mar 2012, Jeremy Morton wrote: >> On Thu, Mar 8, 2012 at 11:33 AM, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > >> > 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html