Transfer from a personal account to an org: what happens to projects #151297
-
Select Topic AreaQuestion BodyHi. To later migrate the project, I see there's gh-migrate-project, that should do. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
|
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. so summarizing repo moves, project doesn’t, issue links break. |
Beta Was this translation helpful? Give feedback.
-
|
Here's a detailed breakdown of what happens when transferring repositories with GitHub Projects and your options: 1. Repository Transfer Impact on Projects
2. Post-Transfer OptionsOption A: Keep Using Original Project
Option B: Migrate Project Properly# Using GitHub CLI for project migration
gh extension install github/gh-migrate-project
gh migrate-project --source-owner PERSONAL_ACCT --target-owner ORG --project-number 123Requirements:
3. Recommended Workflow
4. Key Considerations
5. Alternative SolutionCreate a new project in the Org and manually: 1. Export old project to CSV: `gh project --owner PERSONAL_ACCT -p 123 view --format csv > backup.csv`
2. Import to new Org project
3. Update repo references in new project |
Beta Was this translation helpful? Give feedback.
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.
…