I do actually think this is reasonable. It's really annoying when the handle you want is taken by someone who hasn't used it for years.

Two years might be a little short though.

It feels a little different if — as it seems to be the case — the GitHub account is used as a static site generator. Heck, the guy could've been depending upon CNAMEing to `rbishop.github.io`.

> It's not like you paid for it.

There are individuals that pay ~$4/month for GitHub Teams, plus other services (Copilot, CI, LFS, Packages, etc). They may not have public repos, but that shouldn't matter.

You are talking about something different.

I doubt GitHub is going to close the account of an actively paying user. Rather, the fact that they are paying for it constitutes proof that the account is actively owned.

Weird not to notify the original owner and give him a chance to respond though.

Yeah I think this is the real issue at hand.

Why did the Github support add an ssh key, though?

Added to the account after it was transferred to its new owner.

Why would it show up in the Security History events for rbishop-xx, then?