-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notification filtering #772
Comments
fwouts
added a commit
that referenced
this issue
Jun 4, 2020
This is a variant of "Mute until next update" that ignores new commits. See #772.
fwouts
added a commit
that referenced
this issue
Jun 4, 2020
This is a variant of "Mute until next update" that ignores new commits. See #772.
fwouts
added a commit
that referenced
this issue
Jun 4, 2020
fwouts
added a commit
that referenced
this issue
Jun 4, 2020
Giving it a bit more thought, this feature isn't quite what you need, because it only affects PRs that you have muted. It won't affect PRs that you have reviewed, and that automatically disappear from "Incoming PRs" because you have reviewed them. I guess we'll need these notification settings after all :) |
fwouts
added a commit
that referenced
this issue
Jun 4, 2020
fwouts
added a commit
that referenced
this issue
Jun 4, 2020
Ah, that latest commit should do nicely :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the vast majority of cases, I am not interested in when the author has added a new commit. I'm interested when they tag me, request a review from me, or comment on a PR which I've been involved in. A large part of my interaction with PR Monitor seems to be "mute until next update from author" when they add a commit (it's especially annoying when it's just that they've merged the latest master into their branch).
A way to select which notifications I'm actually interested in would be nice. This includes the badge on the icon - it should only increase its count for notifications I've selected.
The text was updated successfully, but these errors were encountered: