kaiyuanshe / kaiyuanshe/osschat

consider blacklist feature

Open
#116 0 comments 0 reactions 1 assignee Claimed by @jixuan1989 View on GitHub
pull request welcome
Dominant language
TypeScript
Stars
186
Forks
45
PR merge metrics
No merged PRs in 30d

Description

Hi, how about considering adding a new feature to screen someone?

In our project, IoTDB, we are using Sonar to check the code quality.
Then, for each PR (and for each update after a PR is opened),
the Sonar robot will leave a comment to say whether the PR has code quality problems.

We like the feature. But.... as some PRs have problems and the committer may update it many times, we receive a... message bomb...

![image](https://user-images.githubusercontent.com/1021782/80085835-620a1e00-858b-11ea-8f12-5cf72d81ab66.png)

So, if we have a blacklist feature, we can screen the message from a specific user (in many cases it is a robot).

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.