To transfer an open issue to another repository, you must have write access to the repository the issue is in and the repository you're transferring the issue to. For more information, see "Repository roles for an organization."
Note: You can only transfer issues between repositories owned by the same user or organization account. A private repository issue cannot be transferred to a public repository.
When you transfer an issue, comments and assignees are retained. Labels and milestones are also retained if they're present in the target repository, with labels matching by name and milestones matching by both name and due date. This issue will stay on any user-owned or organization-wide project boards and be removed from any repository project boards. For more information, see "About projects (classic)."
People or teams who are mentioned in the issue will receive a notification letting them know that the issue has been transferred to a new repository. The original URL redirects to the new issue's URL. People who don't have read permissions in the new repository will see a banner letting them know that the issue has been transferred to a new repository that they can't access.
Transferring an open issue to another repository
On GitHub.com, navigate to the main page of the repository.
Under your repository name, click Issues.
In the list of issues, click the issue you'd like to transfer.
In the right sidebar, click Transfer issue.
Select the Choose a repository dropdown menu, and click the repository you want to transfer the issue to.
Click Transfer issue.
To learn more about GitHub CLI, see "About GitHub CLI."
To transfer an issue, use the
gh issue transfer subcommand. Replace the
issue parameter with the number or URL of the issue. Replace the
owner/repo parameter with the name of the repository that you want to transfer the issue to, such as
gh issue transfer ISSUE OWNER/REPO