Agreed this would be really good to have; also to move multiple issues from project A to project B as there is a limit on number of issues in one project (1200).

bump

Any news on this?

At this time, GitHub does not have a built-in feature to move multiple issues from one repository to another in a single operation. However, there are a few workarounds that may be helpful.

One option is to use a third-party tool like the GitHub Issue Mover, which allows you to move multiple issues at once between repositories. Another option is to use the GitHub API to automate the process of moving issues using a script or tool.

Keep in mind that both of these options require some technical expertise and may have limitations depending on your specific use case. It's always important to test any changes thoroughly and ensure that you have backups of your data before making any significant modifications.

Hope this helps! 🙌🙌

Would another solution then be to make a full backup of the repository?

Move all your repositories to a monorepo they said... it will be fun they said!

I just found this whilst searching for similar issues before creating the same post myself. It would be a very helpful feature.

Still difficult today 💀

bump

This feature would greatly help us, too, in both private and public repositories.

easily done by a script like this:

cd /location/where/you/cloned/the/source-repo
$issues = (gh issue list --state all --json number --limit 1000) | ConvertFrom-Json

foreach($issue in $issues){
   gh issue transfer $issue.number <owner>/<target-repo>
}

Dear @github @community team,

This ticket is really important.

Thanks in advance.

It is linked to:

• https://github.com/orgs/community/discussions/5766

Note, that the proper solution will allow also copy of the issues in case of organization change. Then the simple transfer is getting slightly complicated.

bump

Bump