4 ms·
Probably because removing branches from the remote doesn't make the commit history inconsistent with any copies made before the push. That seems to be the only
by ziml77 6y ago
Probably because removing branches from the remote doesn't make the commit history inconsistent with any copies made before the push. That seems to be the only case where git second-guesses what you tell it to do.