3 ms·
Yeah I understand how this is unfortunate but for 99% of cases this is what you want to happen when you remove someone's access to a private codebase. It seems
by chrisfosterelli 4y ago
Yeah I understand how this is unfortunate but for 99% of cases this is what you want to happen when you remove someone's access to a private codebase.
It seems like this is an unusual use case that OP had an MIT-licensed open source project whose source only exists in a private repo.
- cma 4y agoIs this scenario possible? - you fork a public repo - it's visibility is changed to private but you have access through the org - they delete it - you lose your fork, which was only ever of the public repo
- kitkat_new 4y agono, in this case it works as expected; "GitHub will detach public forks of the public repository and put them into a new network. Public forks are not made private." https://docs.github.com/en/repositories/creating-and-managing-repositories/about-repositories https://docs.github.com/en/repositories/creating-and-managin... But better be safe than sorry...