Dry run of ownership transfer

[chrisjkuch]

Dry run of ownership transfer

[chrisjkuch]

Looks like this will just work. Some other thoughts on transfer notes here:

If the transferred repository contains an action listed on GitHub Marketplace, or had more than 100 clones or more than 100 uses of GitHub Actions in the week prior to the transfer, GitHub permanently retires the owner name and repository name combination (OWNER/REPOSITORY-NAME) when you transfer the repository. If you try to create a repository using a retired owner name and repository name combination, you will see the error: "The repository REPOSITORY_NAME has been retired and cannot be reused."

I don't think we care about this.

When you transfer a repository from a personal account to an organization, issues assigned to members in the organization remain intact, and all other issue assignees are cleared. Only owners in the organization are allowed to create new issue assignments.

Don't think this will be an issue

If the transferred repository contains a GitHub Pages site, then links to the Git repository on the Web and through Git activity are redirected. However, we don't redirect GitHub Pages associated with the repository.

This might matter? I'm also not sure I fully understand the distinction here.

Warning: If you create a new repository or fork at the previous repository location, the redirects to the transferred repository will be deactivated. They can be reactivated by renaming or deleting the new repository or fork.

Let's just make sure we not do this, but I don't imagine we will and even if we tried we'd likely be stopped because of the first quoted block.

[jayqi]

If the transferred repository contains a GitHub Pages site, then links to the Git repository on the Web and through Git activity are redirected. However, we don't redirect GitHub Pages associated with the repository.

This might matter? I'm also not sure I fully understand the distinction here.

Yes, this will matter. GitHub's lack of support for this is unfortunate, and there's a workaround that doesn't perfectly fix things but is probably sufficient. It's the GitHub-pages-related checklist item in this issue #315