Offer option to relink all independent, duplicate repos as forks

[TPS]

@github (@microsoft?) should go back & permanently offer an option to relink all complete (issues, pull requests, histories, & all!) independent, duplicate projects (many described as "Automatically exported from code.google.com/p/") as proper forks to:

1. the official project, if hosted or regularly mirrored on GitHub, or, failing that,
2. the most notable fork, based on whatever algorithm they choose while implementing Active forks highlighter #562.

Also, this requires solving #129 to behave a bit more sanely, if top fork is chosen as a private repo, or require such top forks always be public.

Background that birthed this issue:
Since Google Code shutdown, there are some hundreds, if not thousands, of duplicate projects scattered all over GitHub from using the Google Code to GitHub exporter tool. Obviously, the tool didn't clearly have the sense capability to create forks, so all these projects are completely independent. Many times, 1 of these is the official project by original developer(s), or at least by a dedicated bunch of users.

[cirosantilli]

For Google code, were forked projects more integrated, or just separate projects just like on GitHub?

I would just do an "import all issues / PRs / branches from given repo" feature, otherwise you will potentially end up importing a lot of trash if you import from all.

[TPS]

I've no idea if forking was even actually a real attribute on GCode (& can't find any info saying so).

As for importing.… I specifically don't want to rearrange issues, &c, due to the specific problem of cross-trashing repos. Just relinking, with hopes of possibility of improved issues/PRs.

[TPS]

Standard form answer received 😞:

Hello,

Thanks for the suggestions! I'll certainly pass them along to the team. I can't promise if/when we might implement them, however your feedback has definitely been recorded.

Let us know if you have any other questions!

Cheers,
GitHub Support