consider detaching this fork from upstream
dwijnand opened this issue · 3 comments
there are downsides to having a live fork also be a fork within GitHub because, for instance, it affects your ability to use GitHub search on the code:
https://github.com/rust-lang-nursery/highfive/search?q=reviewer&type=Code
however, it's possible to request that the repo be made a standalone repository:
To detach the fork and turn it into a standalone repository on GitHub, contact GitHub Support. If the fork has forks of its own, let support know if the forks should move with your repository into a new network or remain in the current network. For more information, see "About forks."
I was able to follow this process to detach a fork with the following message:
Hi GitHub Support!
As detailed in https://help.github.com/articles/why-are-my-contributions-not-showing-up-on-my-profile/#commit-was-made-in-a-fork, please could you detach https://github.com/sbt/sbt-launcher-package from https://github.com/paulp/sbt-extras, turning it into a standalone repository. Note I co-maintain both, but they're distinct entities at this point.
Also, any fork of sbt/sbt-launcher-package should move with sbt/sbt-launcher-package into a new network, rather than remain in the current network.
Thank you,
Dale
Interesting, I did not realise that was possible. I have contacted GitHub support, so hopefully this can happen soon.
done:
