-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
"Only Email on Mention" settings is broken #12774
Labels
Comments
We need a new mock mail sender for tests. |
ref #7813 |
a1012112796
added a commit
to a1012112796/gitea
that referenced
this issue
Sep 9, 2020
fix go-gitea#12774 Signed-off-by: a1012112796 <[email protected]>
techknowlogick
added a commit
that referenced
this issue
Sep 9, 2020
* fix mail mention bug fix #12774 Signed-off-by: a1012112796 <[email protected]> * fix test Co-authored-by: techknowlogick <[email protected]>
a1012112796
added a commit
to a1012112796/gitea
that referenced
this issue
Sep 10, 2020
* fix mail mention bug fix go-gitea#12774 Signed-off-by: a1012112796 <[email protected]> * fix test Co-authored-by: techknowlogick <[email protected]>
lafriks
pushed a commit
that referenced
this issue
Sep 10, 2020
* fix mail mention bug fix #12774 Signed-off-by: a1012112796 <[email protected]> * fix test Co-authored-by: techknowlogick <[email protected]> Co-authored-by: techknowlogick <[email protected]>
Hi guys, I'm getting this exact issue in 1.13 RC1 as well. I think this patch would be in 1.13, but maybe I'm missing something, or maybe this is a new bug. Thanks in advance, |
4 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[x]
):Description
When going to your account settings and choosing the “Only Email on Mention” settings, the will be no Emails sent at all, even if mentioned
We tried this on try.gitea.io and had the same problem. EMails are send out if you choose the standard setting to get notified always. And in that case the Emails also says that you have been mentioned.
https://codeberg.org/Codeberg/Community/issues/257
The text was updated successfully, but these errors were encountered: