libretro / libretro-meta

The Unlicense
4 stars 3 forks source link

Move all the core issues to libretro-meta #78

Closed andres-asm closed 2 years ago

andres-asm commented 7 years ago

We should continue moving all the core issues to libretro-meta to have a single point to track everything https://github-issue-mover.appspot.com/

--- There is a **[$5 open bounty](https://www.bountysource.com/issues/44198968-move-all-the-core-issues-to-libretro-meta?utm_campaign=plugin&utm_content=tracker%2F56438981&utm_medium=issues&utm_source=github)** on this issue. Add to the bounty at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F56438981&utm_medium=issues&utm_source=github).
RobLoach commented 7 years ago

https://github.com/google/github-issue-mover

thatman84 commented 7 years ago

Who can do this? I guess there is a level of access needed

john-parton commented 3 years ago

GitHub now has a "Transfer issue" feature. More info here: https://docs.github.com/en/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository

keithbowes commented 2 years ago

It seems that would make it far harder to search and report issues, for developers of cores to be notified about them, to close issues in PRs, etc.

RobLoach commented 2 years ago

I agree... As a core maintainer, I want issues relating to one core to belong to that core's project. I'd rather use something like the Issue report, or GitHub Projects.