-
Notifications
You must be signed in to change notification settings - Fork 20
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
GitPOAP has notified same user at least 4 times on one repo this year #38
Comments
Twice today |
we are on it - we'll be changing this behavior to make it less nagging. definitely apologize for the annoyance on this - i too don't like getting notified too many times for the same thing. cc @burz ~ are the changes released? |
Hey all, we've just now updated the bot so it won't re-notify a user for PRs that were merged, unless they were explicitly tagged by an owner of the repository. Essentially this means that a user will be notified the first time they become eligible, but won't be notified again on additional merged PRs even if they haven't completed the claim. |
Awesome! Thanks so much! |
thank you for the valuable feedback btw! all feedback is a gift 🎁 in our eyes. |
trufflesuite/ganache#3890
trufflesuite/ganache#4003
trufflesuite/ganache#3351
trufflesuite/ganache#4003
Maybe something weird is going on in their account?
Or maybe they haven't claimed and this is intended behavior of the GitPOAP bot? If that's the case, it's a bit annoying -- as the user might not want to (or can't) claim, and this notification comes off as nagging.
The text was updated successfully, but these errors were encountered: