Gihub has a restriction on forking where an account can only have one fork of a given repository. If you try forking it again, it points to the existing fork.
This means that currently if there is a helpful base project a developer wants to use as the starting point for multiple different apps, they can only initialize the project with dot mod once.
To solve this, we should replace forking with:
- Create a new repo with
gh cli
- Clone new repo into
./
- Clone the other repo into /tmp &
cp its contents in new repo
- Push contents to new repo
This loses the fork ui in github which I don't think we should be concerned about. We can insert some metadata that losely tracks this in the playground's bulletin metadata
Gihub has a restriction on forking where an account can only have one fork of a given repository. If you try forking it again, it points to the existing fork.
This means that currently if there is a helpful base project a developer wants to use as the starting point for multiple different apps, they can only initialize the project with
dot modonce.To solve this, we should replace forking with:
ghcli./cpits contents in new repoThis loses the fork ui in github which I don't think we should be concerned about. We can insert some metadata that losely tracks this in the playground's bulletin metadata