Sitaram Chamarty [off-list ref] writes:
Pushing to delete a non-existent ref (git push origin :refs/heads/foo)
works without error, except for a warning that the remote is "Allowing
deletion of corrupt ref". By "works" I mean all hooks are also
executed.
Is this expected/supported behaviour? Can I rely on it continuing to
work, especially in terms of executing hooks.
This most definitely is just "we didn't bother checking the error too
carefully, especially because the result of deleting something that did
not exist in the first place is a no-op; anybody who tries to delete a
non-existing thing is a moron and deserves whatever random result he
gets".
It would be a good idea to tighten it.
On Fri, Sep 23, 2011 at 11:46 PM, Junio C Hamano [off-list ref] wrote:
Sitaram Chamarty [off-list ref] writes:
quoted
Pushing to delete a non-existent ref (git push origin :refs/heads/foo)
works without error, except for a warning that the remote is "Allowing
deletion of corrupt ref". By "works" I mean all hooks are also
executed.
Is this expected/supported behaviour? Can I rely on it continuing to
work, especially in terms of executing hooks.
This most definitely is just "we didn't bother checking the error too
carefully, especially because the result of deleting something that did
not exist in the first place is a no-op; anybody who tries to delete a
non-existing thing is a moron and deserves whatever random result he
I'd better hide behind the fact that I am only doing it for the
side-effect then ;-)
gets".
It would be a good idea to tighten it.
Thanks. I just needed to know if I could rely on it long-term or not.
I'll find some other way to "poke" a remote repo to run the hooks.