-
Notifications
You must be signed in to change notification settings - Fork 277
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
Refactor notify_snatch to use title, message instead of episode name #5584
Conversation
DeepCode analyzed this pull request. |
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.
Ive merged the join pr. Can you also cleanup that after a develop merge rebase.
Yes, no problem. Will need some more time for this PR. |
DeepCode analyzed this pull request. |
|
||
msg['Subject'] = 'New Login from IP: {0}'.format(ipaddress) | ||
msg['Subject'] = '{0}: {1}'.format(title, ipaddress) |
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.
These new subjects are somewhat less informative then the old. Whas that on purpose?
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.
Ow i swe that these gave all been added to notifystrings. Never mind.
PR is based on the DEVELOP branch
Don't send big changes all at once. Split up big PRs into multiple smaller PRs that are easier to manage and review
Read the contribution guide
Includes: Refactor of email notifications. Should fix: [APP SUBMITTED]: BraceException: Email notifier parsed "{0}" into {1!r} #5583