Open bswck opened 5 months ago
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.
I'll try to develop these routines in jaraco.develop
. It will filter out projects not labeled with [fork]
and migrate these.
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
Need help: #2.
From @jaraco: