What if I just cloned the repo, created a repo of the same name under my own account and then pushed up my local clone to the new repo?
Nothing is stopping you from doing that. The preferred experience is not to do it though.
I should have completed my question in my earlier post. Specifically, would doing that instead of creating a fork through Github's interface prevent one from losing access to their project when the previous copy is deleted from Github?
Yes.
In what way? Genuinely curious
For instance, you'd be able to create private forks in an organization without paying for the Github organization, then keep this private fork once the original membership is canceled.
They could give you an option to make it public, if this is the concern.
Removing access to the fork in that instance would make sense, but that's not what happened here. The author didn't fork in an organisation, he forked to his own personal Premium account. Which he continues to pay for.
OP states that he still has unlimited private repos (presumably on a paid account) so it wouldn't be cheating the private repo limit in this case. GitHub could simply count a forked private repo against the account's private repo limit if the upstream repo is disabled to avoid the type of cheating I'm thinking of.
I haven't paid for private repos (at least not for a few years) and yet I'm a member of several ... and I can fork them as needed without paying. In my case, I would expect that I would lose access to my fork if the private repo was no longer a paid account.
Right, but I'm saying GitHub could allow you to keep accessing those cloned repos if the upstream repo was disabled as long as you switch to a paid plan. I.e. they could treat it the same way they treat your own private repos when you go from a paid to unpaid plan.
Yes ... it could be that if either of the private repos was paid, they would be available.
Not totally following you on this. Do you mean the system as in terms of Github's profit model?