Repository navigation
feat: Add no-reply notice and reply-to to automated emails - #823
Merged
goelsonali merged 1 commit intoOct 19, 2026
Merged
goelsonali merged 1 commit into
goelsonali merged 1 commit into
Conversation
violazeneli31
requested review from
OlenaReukova,
Sowmiya07,
Tooonia,
dricazenck,
goelsonali,
lauracabtay and
nverbic
October 16, 2026 19:42
violazeneli31
force-pushed
the
feature/821-automated-email-footer
branch
from
October 16, 2026 19:53
1ede482 to
78c596e
Compare
|
khairahscorner
approved these changes
Oct 17, 2026
khairahscorner
left a comment
khairahscorner
left a comment
Contributor
There was a problem hiding this comment.
LGTM! The PR description was well-detailed too👍
goelsonali
approved these changes
Oct 17, 2026
goelsonali
left a comment
goelsonali
left a comment
Contributor
There was a problem hiding this comment.
Great work !! Clear and well explained.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Changes:
app.email.team-signatureinapplication.yml): "[Automated Message] Please do not reply to this email, as this address is not monitored. For any questions, please contact the Mentorship team at mentorship@womencodingcommunity.com."[Automated Message]line from the 6 templates that had it, so it doesn't show twice.EmailServicenow sets Reply-To to the mentorship email (notification.mentorship-email) when an email has no reply-to of its own. Emails that set their own reply-to keep it.EmailServiceTest(default Reply-To, custom Reply-To kept) and 1 integration test inEmailTemplateServiceTest(the notice appears in rendered emails).Why is this change required?
Mentors and mentees get automated emails from a no-reply address, but nothing told them not to reply, so they were confused about how to contact the mentorship team.
What problem does it solve?
Every automated email now clearly says not to reply and gives the right address. And if someone replies anyway, the reply goes to mentorship@womencodingcommunity.com instead of being lost.
Notes:
[Automated Message]footer, but all 39 use{{teamEmailSignature}}, so adding the notice to the signature covers every automated email.Related Issue
Closes #821
Change Type
Screenshots
Tested locally with the QA Docker stack and MailHog, using the password reset email (a template that never had the old footer). These are email screenshots instead of Swagger, since the change is in the email content and headers.
Notice at the bottom of the email:
Headers showing From: noreply and Reply-To: mentorship@womencodingcommunity.com:
Pull request checklist
Please check if your PR fulfills the following requirements: