Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Negatives of repo being marked as a fork #21

Open
Venryx opened this issue Nov 18, 2019 · 2 comments
Open

Negatives of repo being marked as a fork #21

Venryx opened this issue Nov 18, 2019 · 2 comments

Comments

@Venryx
Copy link

Venryx commented Nov 18, 2019

Just wanted to mention that there are some negatives to having your repo marked as a fork, if you plan to have it up for the long-term:

  1. You can't use the search function (an annoyance I've hit with other forks that "became the main" before)
  2. I believe it also deprioritizes the repo in search results.

So it may be worth deleting and recreating the repo as a "source" repository, before too many people star/watch/fork it.

@dmurvihill
Copy link
Owner

Thanks, noted. Let's try and do that after the name dispute is complete as we won't properly be the main until then.

@Venryx
Copy link
Author

Venryx commented Oct 15, 2020

I found out that apparently you can ask GitHub support to disconnect a forked repo from the source repo: https://docs.github.com/en/free-pro-team@latest/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile#commit-was-made-in-a-fork

Certainly better than deleting and recreating. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants