Refined-github: Removing +1 from GitHub Issues

[pavsidhu]

The number of +1 comments on issues make it difficult to read through issues and get to the information that's important. I'd be up for adding functionality to hide +1 comments from issues.

Let me know if this is a good suggestion and I'll get started.

[yakov116]

See #1231 and #1276

[FranklinYu]

I would also like a bot that

1. Watch my repositories for +1.
2. Delete those comments.
3. Send an email to those users and explain about this.

[Kocal]

@franklinyu I don't really think Refined GitHub can do that, you should write your own bot or use webhooks.

However, dynamically hide "+1"/"-1" post seems to be a good idea.

[fregante]

I think +1's can be hidden selectively.

• The noisy +1's are usually left by random people who stumble on a thread.

• Useful +1's may instead be by a team member or a someone who's having a conversation, e.g. "Deploy?" "+1"

In short, hide +1 comments unless:

• they have a label (owner/contributor/etc), or
• they left a comment before the +1

for (const comment of select.all('.comment-body > p:only-child')) {
    if (/^(\+1|👍)$/.test(comment.textContent.trim())) {
        const container = comment.closest('.js-timeline-item');
        if (!select.exists('.timeline-comment-label', container)) {
            container.hidden = true;
        }
    }
}

Testing ground: https://github.com/hayaku/hayaku/issues/303

Previous feature: https://github.com/sindresorhus/refined-github/pull/159

It might also be nice to have a note before the comment box saying "N annoying comments removed", which when clicked will revert .hidden

[lukehefson]

Hello folks! The Papercuts team at GitHub just shipped https://blog.github.com/changelog/2018-09-24-hiding-repeat-comments/ as a way to help with this problem! I'm hoping that it doesn't cause too much havoc with y'alls implementation 😬.

In the future, we _might_ iterate towards something more like the refined-github way of doing this – so watch this space!