Pretty bizarre behaviour given how easy it is to get around this. Instead of forking, just git remote set-url origin <new-remote-repo> The new remote can even

Pretty bizarre behaviour given how easy it is to get around this. Instead of forking, just git remote set-url origin <new-remote-repo> The new remote can even still be on GitHub. So what’s the point? Anyone relying on this to retroactively remove access to source code has a false sense of security.