Why not use the standard github method? You create an empty Subaru-PFS repo, the other person adds that as a remote and pushes to it. Done. That also has the advantage of working with non-github repos.

if you already have a repo in github, 'transfer' is the standard way in github.

The way GitHub puts it, you can: "Transfer this repository to another user or to an organization where you have the ability to create repositories.". I don't have that ability, so the one-step method does not work. OK.

We have previously, many times, used a two-step method: a Subaru-PFS admin creates the repo and the requesting user pushes to that new remote. When you create a GitHub repository, that is one of the cut-and-pasteable recommendations they immediately suggest. This method also works for non-github repos, as has been needed several times.

I understand that some users might not actually use raw git, in which case you might need a more complicated scheme. But I don't know of any in this project.

I want to state just one point, if you already have repository on github, we are better to complete all within github not to miss or lose any additional or attached information but not in the git tree itself. So, that's why I am proposing in this ticket.

We have since settled on letting the developer push to a new repo. Direct.