It probably doesn't help that GitHub's OAuth scopes seem to be rather shotgun: https://developer.github.com/v3/oauth/#scopes . It seems you can't just ask for read-only access to, say, a list of commit hashes that would prove you've been working on a project without disclosing what you've actually been doing.
Still, I think that button's deserving of a red flashing "only click this if you're sure you won't be fired and sued into bankruptcy" banner.
Note that we also offer the ability to connect to what is already publicly visible via GitHub if you don't want to grant us full access.
I don't think this is true, and if it is, it shouldn't be. I certainly wouldn't care if a candidate didn't have anything to share on GitHub.
Your reasoning makes sense, and it's perfectly fine to do it the way you are. I think people like me are just pointing out that this makes us self-exclude ourselves from the site, in case you wanted us.
Edit: As a follow-up, how do I remove a github reference once it was set up? I couldn't find it in the update options :)
As for removing GitHub, that's a good catch. We should provide a way for the user to _detach_ their accounts as well as indicate that they don't have said accounts.
Thanks for the feedback!