[johndbritton]

Hey Niels!

I'm John, and I work at GitHub. Sorry to hear you're having difficulty.

From your post:

> I haven’t tried contacting customer support, but as this appears to be official policy I would not expect a change there.

I'd recommend you reach out to [e-mail], they're usually very helpful with things like this.

[nielsole]

Hey John,

thanks for reaching out. The individual case was resolved (found a local copy). But I find the policy worrisome for future projects. If the customer support was happy to reenable access for me, what is the point of the current policy?

[crankylinuxuser]

That's why I've been migrating my Github/lab projects to IPFS as well. I have a few cheap VPSes I have my stuff pinned.

"Cloud" (read: someone else's server) is unreliable at best, or malicious at worst like this case. The people may not be bad actors, but the tech definitely is.

[bringtheaction]

Would like to hear more about your git with IPFS workflow.

[icebraining]

How are VPSs not on someone else's server too?

[kercker]

If people can get the fork back after reaching out to [e-mail], why would not GitHub resolve this issue once and for all, so that people will not need to reach out to [e-mail] any more?

[philipwhiuk]

If Support just do this kind of thing why not put it in the UI. It's like unlinking a fork - GitHub Support just do it on asking - but why is GitHub spending unnecessary manpower when it could just be a button in the settings saying 'Unlink'.