-
Notifications
You must be signed in to change notification settings - Fork 60
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
fix-138: Change added as a speaker email #143
Conversation
Reviewer's Guide by SourceryThis pull request addresses issue #138 by updating the email template used to invite speakers. The changes include a more welcoming greeting, a detailed and encouraging body, and a new closing line. Additionally, the email subject has been updated to be more inviting. File-Level Changes
Tips
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @it-tma-tri - I've reviewed your changes - here's some feedback:
Overall Comments:
- Consider adding a unit test for the email content generation to ensure consistency and make future modifications easier to verify.
Here's what I looked at during the review
- 🟡 General issues: 3 issues found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.
You have been set as the speaker of a proposal to the Call for Participation | ||
of {event}, titled “{title}”. An account has been created for you – please follow | ||
this link to set your account password. | ||
We are excited to inform you that you have been selected as a speaker for {event} with your proposal titled "{title}". To get started, an account has been created for you. Please follow the link below to set your account password: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion: Consider breaking the long sentence into two.
The sentence is quite long and could be more readable if broken into two. For example: 'We are excited to inform you that you have been selected as a speaker for {event} with your proposal titled "{title}". To get started, an account has been created for you. Please follow the link below to set your account password.'
We are excited to inform you that you have been selected as a speaker for {event} with your proposal titled "{title}". To get started, an account has been created for you. Please follow the link below to set your account password: | |
We are excited to inform you that you have been selected as a speaker for {event} with your proposal titled "{title}". | |
To get started, an account has been created for you. Please follow the link below to set your account password: |
|
||
{invitation_link} | ||
|
||
Afterwards, you can edit your user profile and see the state of your proposal. | ||
Once you have set your password, you can log in to edit your user profile and track the status of your proposal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion: Clarify the login instructions.
Consider specifying where the user should log in. For example: 'Once you have set your password, you can log in on our website to edit your user profile and track the status of your proposal.'
Once you have set your password, you can log in to edit your user profile and track the status of your proposal. | |
Once you have set your password, you can log in on our website to edit your user profile and track the status of your proposal. |
The {event} orga crew""" | ||
We look forward to your participation and contribution to {event}. | ||
|
||
Best regards, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion: Consider using a consistent sign-off format.
The sign-off 'Best regards, The {event} Organizing Team' is friendly, but consider if it aligns with other communications sent by the team. Consistency in tone and format can help maintain a professional image.
Not sure why this was closed. It seems you changed the correct email, but you did not test the correct email. |
This PR closes/references issue #138 It does so by changing the text as required.
How has this been tested?
Manual tested and received email as follow:
Checklist
Summary by Sourcery
This pull request updates the email text sent to newly added speakers, enhancing the message's clarity and tone. The subject line and body of the email have been revised to provide a more welcoming and informative message.