3 ms·

This is probably the biggest impact, I just wrote on another comment that this didn't seem to be too destructive but it's a bit more of a headache than it seems

This is probably the biggest impact, I just wrote on another comment that this didn't seem to be too destructive but it's a bit more of a headache than it seems. > Current forks will remain public and will be detached from this repository. If I'm not mistaken when they are back public again everyone will need to update their origin ?

morpheuskafka 2y ago
If you have a local git origin set to the HTTPS URL of the parent repo, I don't think anything would change when it comes back online. This sentence seems to be about GitHub internally treating forked repos as branches of the original repo to save space (as well as displaying "fork of X" in the UI), and there's no way to manually set that relationship other than the fork button. GitHub would have to manually reset that if they wanted to. (This setup is what allows those fake commit URLs where you use the URL of the original repo plus the commit hash of a commit in a fork.)