Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Tracking bug for issue bot improvements #14616

Closed

Description

@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.

Activity

  1. strugee commented on Feb 13, 2018

    @strugee
    ContributorAuthor
  2. Bisaloo commented on Feb 13, 2018

    @Bisaloo
    Collaborator

    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.

  3. strugee commented on Feb 14, 2018

    @strugee
    ContributorAuthor

    @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.

  4. Bisaloo commented on Feb 18, 2018

    @Bisaloo
    Collaborator
    • 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.

  5. strugee commented on Feb 18, 2018

    @strugee
    ContributorAuthor

    @Bisaloo see the second item in the list.

  6. added a commit that references this issue on Feb 20, 2018
  7. added a commit that references this issue on Mar 21, 2018
  8. added a commit that references this issue on May 16, 2018
  9. pipboy96 commented on Mar 31, 2019

    @pipboy96
    Contributor

    The bot seems to have been disabled.

  10. strugee commented on Apr 16, 2019

    @strugee
    ContributorAuthor

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

  11. pipboy96 commented on Apr 16, 2019

    @pipboy96
    Contributor

    @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.

  12. Bisaloo commented on Apr 16, 2019

    @Bisaloo
    Collaborator

    @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

  13. strugee commented on Apr 16, 2019

    @strugee
    ContributorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions