Hilco Wijbenga [off-list ref] writes:
quoted
Some ways you can prevent it from happening again:
(1) setting your canonical repo config to deny non-ff, and deny deletes:
[receive]
denyDeletes = true
denyNonFastforwards = true
I would *really* like to do that but I need access to the server for
that, right? Unfortunately, we use Unfuddle and that means no such
access. So no server config changes and no Git hooks.
receive.denyNonFastforwards is a reasonable thing to ask for
projects with a shared repository workflow, so I suspect hosting
service providers may want to race adding support for it to win
customers. Have you asked them?
On 22 June 2012 16:59, Junio C Hamano [off-list ref] wrote:
Hilco Wijbenga [off-list ref] writes:
quoted
quoted
Some ways you can prevent it from happening again:
(1) setting your canonical repo config to deny non-ff, and deny deletes:
[receive]
denyDeletes = true
denyNonFastforwards = true
I would *really* like to do that but I need access to the server for
that, right? Unfortunately, we use Unfuddle and that means no such
access. So no server config changes and no Git hooks.
receive.denyNonFastforwards is a reasonable thing to ask for
projects with a shared repository workflow, so I suspect hosting
service providers may want to race adding support for it to win
customers. Have you asked them?
I agree and I was thinking of doing exactly that. So after your
friendly nudge I sent them an email.
The first (very prompt) reply said they didn't support "custom hooks".
When I explained that I was not asking for a custom hook but that I
simply wanted a Git setting changed, I was informed (again, very
promptly) that that was quite impossible. :-(
In my opinion, it should be fairly simple for them to create a web UI
to set Git config settings (I can understand they do not want to do it
manually) but they do not seem very interested. A bit surprising and
certainly very disappointing.