Tell HN: GitHub will delete your private repo if you lose access to the original

Re:Tell HN: GitHub will delete your private repo if you lose... by bcrosby95 on Tuesday January 31, 2023 @05:19PM (#34603121)

This is why I don't use github's fork feature. There's more than just this restriction they impose upon you.

Instead I prefer to use a "git" fork. I just clone it and upload it to my own repo. Assuming the license permits of course.

[ Parent | on HN ]

Re:Tell HN: GitHub will delete your private repo if you lose... by ntrz on Tuesday January 31, 2023 @05:27PM (#34603222)

Don't you need to have an "GitHub-approved" fork (i.e. use the GitHub fork button) if you want to create pull requests on the upstream project in GitHub? Or is there a way to do that from the kind of repo you're describing?

[ Parent | on HN ]

Re:Tell HN: GitHub will delete your private repo if you lose... by edaemon on Tuesday January 31, 2023 @05:47PM (#34603453)

If that came up you could create a GitHub-native fork and add that as a remote.

[ Parent | on HN ]

Re:Tell HN: GitHub will delete your private repo if you lose... by dreamcompiler on Tuesday January 31, 2023 @05:46PM (#34603444)

This is the right answer: Break the fork link. I sometimes do this to make a private "fork" of a public repo so that I can add my own notes about how to use it, remind myself what happened when I tried it, add a config script for my own peculiar setup, etc.

It's unfortunate because not having a "real" fork makes it harder to send pull requests and track the upstream. But it's sometimes necessary to get around stupid github policies.

[ Parent | on HN ]