How do I move an issue on github to another repo?
GithubGithub Problem Overview
It happens every now and then. Some library depends on another and a user opens an issue that belongs to the wrong repo. Can I move the issue to the other repo?
You could argue that the issue could be seen as being both repos' issue because one depends on the other and as long as one doesn't work properly both don't. But I'd rather talk about solutions to the issue in the repo it belongs in.
Github Solutions
Solution 1 - Github
No, officialy you can't move issues between repositories.
There is a hack though, github-issues-import, kind of a plugin, to import issues from a repository to another.
Solution 2 - Github
See the GitHub docs on transferring issues.
> # Transferring an open issue to another repository > On GitHub, 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 this issue.
Solution 3 - Github
I've created a Chrome Extension called Kamino that will clone issues from one repository to another. It will also close the original issue. It will also eventually be available for MS Edge.
https://chrome.google.com/webstore/detail/kamino/ffdebockfdjileaojbbccofhgncmioaf?hl=en-US
Solution 4 - Github
If you have the ZenHub integration you will see this button at the very lower-right when viewing an issue. This allows the issue to be copied to another repo in the same organization, or copied and closed.
And yes, "Move Issue" is a misnomer.
There seems to still be no way to move (copy and delete) or to just delete, a mistakenly-submitted issue.
EDIT: Beware, the v1 of this feature has major limitations like leaving behind some(most?) of the issue's metadata, not notifying subscribers, etc.
Solution 5 - Github
This is now (May 2019) easier.
See "Improvements to issue transfer permissions "
> Users with write access to two repositories can now use issue transfer to move issues between them.
Previously, only users with admin permissions on both repositories had the ability to transfer issues.
> In addition, we will no longer allow issues to be transferred from private to public repositories.
See more at "Transferring an issue to another repository".
Solution 6 - Github
The visual answer as taken from github docs:
Transferring an open issue to another repository
- On GitHub, 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.
- Use the Choose a repository drop-down menu, and select the repository you want to transfer the issue to.
- Click Transfer issue.
Solution 7 - Github
Addition to the answer from @MatthewMcCullough.
If you have many issues to transfer doing every one from a browser can be tedious.
You can then use GitHub CLI like this:
gh issue transfer issue owner/repo
> 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 octocat/octo-repo.
Note that:
> The issue's labels and milestones are not retained. This issue will > stay on any user-owned or organization-wide project boards and be > removed from any repository project boards.
https://docs.github.com/en/github-cli/github-cli/about-github-cli