Closed robertoaloi closed 3 years ago
I have a slight preference for #2, just because I'd like to keep my repositories in the same network. What do I need to do to make that happen?
@robertoaloi I don't have a strong opinion on this. I'm OK with both :+1:
Let's go for 2, then. @jkakar I will contact you privately on what's needed from you.
Fixed, thanks to the amazing GitHub support!
Thanks for taking care of this Roberto!
On Sat, Mar 27, 2021 at 9:12 AM Roberto Aloi @.***> wrote:
Fixed!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aws-beam/aws-codegen/issues/75#issuecomment-808755822, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEJRRWRADDFHAHYH2U6INLTFX7XDANCNFSM4ZXE63SQ .
The
aws-codegen
,aws-erlang
andaws-elixir
repos are forks of the respectivejkakar/*
versions. Nowadays, thejkakar
repos are outdated and they point toaws-beam
from their respective READMEs. The current setup is suboptimal since, whenever a PR is raised in one of theaws-beam
repositories,jkakar
is marked as the default "base repository":I contacted GitHub support to check if there is an option to update the base repo, to make contributors life easier. They gave the following two options:
We can extract your forks from the current repository network. This will leave the repositories owned by jkakar as root repositories, but the aws-beam repositories and the child repositories under them would be moved to their own network where the aws-beam repositories are the root. I can do this with just your confirming that this is what you want to do.
We can update the current repository network so that the aws-beam repositories become the root repository for the network and the ones owned by jkakar would become children of those repos. This would leave all repositories currently under the jkakar repositories in the same fork network, but would require permission from jkakar to make the change.
Of course we also have option 3. which is leaving things as they are.
@jkakar @philss Any opinions?