Skip to content
Discussion options

You must be logged in to vote

When transferring a repository from a personal account to an Organization on GitHub, the associated classic projects (if applicable) do not transfer with it. However, the impact depends on the type of project.

If the project was tied to the repo, it stays behind in your personal account, and all the issue/PR references inside it will break since the repo is now in a different location. If it was a user-level project, it still exists, but you can't link it to the new repo in the Org.

For those using the new GitHub Projects (beta), the issues will remain, but you'll likely need to manually re-associate them with the new repo.

Workarounds?

Before transferring, export the project just in case.

Replies: 2 comments 4 replies

Comment options

You must be logged in to vote
1 reply
@maxxer
Comment options

Answer selected by maxxer
Comment options

You must be logged in to vote
3 replies
@maxxer
Comment options

@maxxer
Comment options

@mecodeatlas
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Repositories The core of version-controlled code storage Question Ask and answer questions about GitHub features and usage
4 participants