Move (clone and close) Github issues to a different repository
Published 2017-08-04, 11:45
If you have any projects on Github that span multiple repositories you know the pain when someone creates a valid issue, but uses the wrong repo to do so. Of course you could tell them to „Create another issue in the correct repo and gtfo“ but that a) wouldn’t be very nice and b) is a quite a lot of work and c) probably wouldn’t have the intended effect to grow your Github community.
So you need a way to move issues betweens repos.
Github doesn’t support this out of the box, but of course some other people jumped in and created things that do. Here is an overview of my research on this:
- Github Issue Mover
github-issue-mover.appspot.com / github.com/google/github-issue-mover
Almost a classic, started in 2014, this tools allows you to paste the source issue and target repo to be moved and then does the job. - Kamino
chrome.google.com/webstore/detail/kamino/ffdebockfdjileaojbbccofhgncmioaf / github.com/gatewayapps/kamino
This Chrome extension is „better“ in that it adds the „move issue“ button directly to the Github issue page and also remembers the last 5 used repos. - Zenhub seems to have a „Move Issue“ button if you use their tool.
- github-issues-import is an old but trusty Python script that can do the job for one or many issues.
Topic(s): Link
No comments - :(
Zum Artikel Move (clone and close) Github issues to a different repository sind noch keine Kommentare vorhanden. Deine Meinung wäre jedoch willkommen!