Develop routines to bulk migrate a set of repos

[johnslavik]

From @jaraco:

In order to facilitate the reliable transfer of repos from jaraco to coherent-oss, I'd like to see if we can develop a routine to automate much of the process.
I found this feature request on using the GH CLI to transfer issues. Although it's not supported as a first-class feature, it does describe how to invoke the API to trigger a transfer. It's unclear to me if that merely initiates the transfer or if it enacts it.

[johnslavik]

I've investigated the transferring feature and I'm sure that the request only initiates the transfer, because in case of transferring a repo from an old personal account to a new one it's needed to wait for a consent from the new owner account. Additionally, I've tested the migration of a temporary repo to this org and the response from the GitHub API only presents the old repository data, so I am assuming that the new data remains unknown until the transfer is set—I've seen a note that the transfer process is asynchronous, according to the docs:

The response will contain the original owner, and the transfer will continue asynchronously.

Fortunately, when migrating projects from a personal account to an organization, no additional confirmations are needed.
We can fully automate the process and they have to run on your end.

[johnslavik]

I'll try to develop these routines in jaraco.develop. It will filter out projects not labeled with [fork] and migrate these.

[johnslavik]

It will filter out projects not labeled with [fork] and migrate these.

Wrong. We can weed out projects that are already old along the way and can stay in the @jaraco account as they are no longer maintained. The project list will appear in #3

[johnslavik]

Need help: #2.