Tracking bug for issue bot improvements

[strugee]

Type: code issue

This is a tracking bug collecting all the ideas that have been proposed for the issue format bot, in various issues. Feel free to comment below and I'll edit the description to add ideas to the list.

Issues with high impact and low work factor are prioritized higher.

• [PR Report issue format bot code coverage #14617] Automatically report code coverage when the test suite is run
• Strip domain information when it doesn't make sense for the type
• [PR Improve issue bot wording #15439] Link to the issue template when posting error messages
• [PR Improve issue bot wording #15439] Adjust wording (mathjax.org may need ruleset updated #14654 (comment))
• [PR Have the bot label issues by type #14698] Have the bot autolabel ruleset issues, code issues, etc. (Handling old issues #13890 (comment))
• Didn't label http://(.+\.)?radare\.org/ -> https://$1radare.org/ #15594 correctly
• Allow community members to ask the bot to label an issue as potentially outdated (not sure this is a good idea but would help people with write access find issues to close, see Handling old issues #13890 (comment))
• Allow community members to ask the bot to add metadata to the issue description (Handling old issues #13890 (comment))
• [PR Bump issue bot deps #14635] Update dependencies
• Debug the webhook signature crash (Implement issue labeller bot #11615 (comment))
• Merge the PR labelling bot (Implement issue labeller bot #11615 (comment))
• Have the bot manage incoming ruleset ideas in a separate repository (Handling old issues #13890 (comment))
• Reference other issues/PRs with shared domains (Tracking bug for issue bot improvements #14616 (comment))
• Investigate Probot 4.0's improved logging - https://github.com/probot/probot/releases/tag/v4.0.0
• Clean up the test suite (Expand the bot's test suite #13466)
• Have Travis CI run the bot test suite

[strugee]

/cc @Bisaloo

[Bisaloo]

It would also be useful if the bot could warn the OP when there is another open issue/PR with the same domain.

It would:

• help prevent duplicates
• ensure contributors fix all issues related to a specific domain where they open a PR
• inform users that their issue may already be fixed in a pending PR
• ...

This may be tricky though because it would require the bot to keep a list of domains and to scan all issues/PR every single time.

[strugee]

@Bisaloo that's a good idea. However GitHub doesn't provide a good API for issues search, at least not in APIv3. I think we should be able to just load all the open issues in memory though, if we don't keep any of the issue bodies and basically just map domain -> issue number(s). I'll have to measure the memory consumption but I think it'll be okay - although what if the issue list grows? There are ~500 open issues as of this writing.

[Bisaloo]

• Allow community members to ask the bot to label an issue as potentially outdated (not sure this is a good idea but would help people with write access find issues to close, see Handling old issues #13890 (comment))
• Allow community members to ask the bot to add metadata to the issue description (Handling old issues #13890 (comment))

About this, I would like to be able to label:

• CORS issues
• MCB

Also, the bot should probably label all ruleset issues as such. Right now, we only know this because of Alexa ranks. And it only works if rank < 1M.

[strugee]

@Bisaloo see the second item in the list.

[pipboy96]

The bot seems to have been disabled.

[strugee]

Yeah, I'm curious what happened there? Did it fall over or were people not happy with the way it worked?

[pipboy96]

@strugee Mostly the fact it wasn't well written and created spam comments. I want to try to fix it if possible, so it could be restarted.

[Bisaloo]

@strugee, my understanding it that it fell over and nobody bothered restarting it. You'd need to ask @zoracon for more info.

@pipboy96, wasn't the multiple comment issue fixed? I don't remember very well

[strugee]

Mostly the fact it wasn't well written and created spam comments. I want to try to fix it if possible, so it could be restarted.

If it was creating spam comments I wish someone would've pinged me so I could fix it. Unless you were referring to #13460? But that was fixed over a year and a half ago.