Github silliness

[quickfur]

So, I'm trying to create forks of the forked phobos/dmd so that I can start submitting PRs for them. Turns out, github does not support this because I already have forks of the upstream phobos/dmd, and github does not allow multiple forks of the same project. What kind of silliness is this?! git can handle this just fine (it's two different upstream URLs) but github for whatever reason can't. Sigh.

Anybody know how to work around this? Create a new organization?

[adamdruppe]

i just tried renaming them all maybe that will be enough. a bit of a hassle but not the end of the world

[quickfur]

OK, I figured out a way to do this. Basically, github does not allow you to create multiple forks of the same upstream repo. This means trouble for us, because ldc's phobos fork is forked from upstream, and opendlang's phobos is also forked from upstream. So github won't let you fork the ldc team's phobos into the same account / organization again.

Fortunately, the ldc team uses a specific tag ldc for ldc-specific changes. Which means it should work once you create a branch called 'ldc' in opendlang's phobos fork, then separately pull the ldc team's fork into a local repo and push it to this branch. That will bring their changes to opendlang's phobos fork. Then we can update the ldc fork's .gitmodules file to point to that branch instead of the upstream branch, and it should work.

At least, I think it should. :-D Don't have commit access to opendlang's repos so I can't really test this out yet. I've already created a separate org of my own just so I can fork opendlang's phobos, due to the same silly restriction.

[adamdruppe]

so i guess we can change the names back then?

[quickfur]

Don't think the name itself is very important. What's needed basically is you need to create a branch called ldc, then I can submit a PR to merge in the ldc team's branch. Got your invite to the org but apparently I still don't have commit access to the phobos fork, so can't do it from my end.

[quickfur]

OK, now that we've merged multiple upstream repos into a single repo, there's no longer a direct link with upstream code that I know of. So we can probably clone safely without running into github restrictions anymore. Closing.