Meta issue for FIXMEs that reference closed issues

[oli-obk]

@Eh2406 compiled this awesome list. I think it should be a meta issue. So here it is

https://gist.github.com/Eh2406/b92f034f8adc193894482e19c79d80f1

[Eh2406]

The good part, this was made with an automated script. I can keep it up-to-date by rerunning as often as we want.

The bad part, it was made with an automated script. Some of these are false positives, like the first one, where the script was too dumb to realize said it's an issue on a different Repository.

In general fees can be fixed by:

1. Doing what the fix me said to do and seeing if the pr passes
2. Updating the fix me to refer to a more current issue number
3. Removing the fix me has the issue was closed won't fix

In the past couple of days I have been reviewing some of these, and if I'm not sure what to do I'v leaving a comment on the clothes issue with a link to the fix me asking for advice.

[Eh2406]

Thanks @nivkner! Let me know when I should rerun the script.

[nivkner]

This kind of metabug seems like something that should be tackled continuously, as new FIXMEs are added over time, so if possible this would be better run routinely. Otherwise there really isn't much of a difference between running the script or marking FIXMEs as complete.

Since I wouldn't ask you to dedicate so much time to this one issue, I'd like to know what is your opinion on turning this script into a github bot like "rust-highfive" or "bors". Then whenever an issue is closed, this "FIXME bot" could update this issue.