3 ms·

This is not what people expect, so that's one obvious reason it's very likely the wrong decision. I would have never known this. If you are relying on a public

This is not what people expect, so that's one obvious reason it's very likely the wrong decision. I would have never known this. If you are relying on a public external product on github, you have to go several painful steps to make it 'safe', you have to re-upload it, and there's no good reason to make people do it. It's a giant disincentive to fork things on github. To be safe of finding things later, there will probably be another git repo website that will agree to "host" your forked projects safely, so that you can access them. I understand on the other side, there's value in being able to stop people who forked your code. But it's a very weak stop-ability, because they could just keep the code locally and re-upload.

chc 9y ago
What does this have to do with public projects? This is entirely about private repos.
- Jesus_Jones 9y ago
  My understanding from reading that was that even on a "public" project the owner can delete it, change it's status, and it disappears from availability.
  - chc 9y ago
    Fortunately not. As noted in the article[1] linked in the OP: > Deleting a public repository > When you delete a public repository, one of the existing public forks is chosen to be the new parent repository. All other repositories are forked off of this new parent and subsequent pull requests go to this new parent. > Changing a public repository to a private repository > If a public repository is made private, its public forks are split off into a new network. As with deleting a public repository, one of the existing public forks is chosen to be the new parent repository and all other repositories are forked off of this new parent. Subsequent pull requests go to this new parent. [1]: https://help.github.com/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility/ https://help.github.com/articles/what-happens-to-forks-when-...
    - Jesus_Jones 9y ago
      Thanks for the update. I can't add a post-comment to my question because it's been to long, but I was wrong.

chc 9y ago

What does this have to do with public projects? This is entirely about private repos.

Jesus_Jones 9y ago
My understanding from reading that was that even on a "public" project the owner can delete it, change it's status, and it disappears from availability.
- chc 9y ago
  Fortunately not. As noted in the article[1] linked in the OP: > Deleting a public repository > When you delete a public repository, one of the existing public forks is chosen to be the new parent repository. All other repositories are forked off of this new parent and subsequent pull requests go to this new parent. > Changing a public repository to a private repository > If a public repository is made private, its public forks are split off into a new network. As with deleting a public repository, one of the existing public forks is chosen to be the new parent repository and all other repositories are forked off of this new parent. Subsequent pull requests go to this new parent. [1]: https://help.github.com/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility/ https://help.github.com/articles/what-happens-to-forks-when-...
  - Jesus_Jones 9y ago
    Thanks for the update. I can't add a post-comment to my question because it's been to long, but I was wrong.