-
-
Notifications
You must be signed in to change notification settings - Fork 775
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
Add send_weekly_recap to crontab #4604
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4604 +/- ##
==========================================
- Coverage 30.12% 30.09% -0.04%
==========================================
Files 210 210
Lines 16911 16911
Branches 2284 2284
==========================================
- Hits 5095 5089 -6
- Misses 11619 11625 +6
Partials 197 197
Continue to review full report at Codecov.
|
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #4604 +/- ##
==========================================
- Coverage 30.12% 30.09% -0.04%
==========================================
Files 210 210
Lines 16911 16911
Branches 2284 2284
==========================================
- Hits 5095 5089 -6
- Misses 11619 11625 +6
Partials 197 197
Continue to review full report at Codecov.
|
@iamonuwa could you
^ this is to ensure the reviewer has enough info to review this PR to merge it in |
@thelostone-mc, I figured it was the remaining piece of the puzzle after with @kuhnchris and |
whats the reference issue? are we sure the weekly recap email is high quality enough that we're ready to send it to everyone? |
… On Tue, 11 Jun 2019, 20:51 Kevin Owocki, ***@***.***> wrote:
whats the reference issue?
are we sure the weekly recap email is high quality enough that we're ready
to send it to everyone?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4604?email_source=notifications&email_token=ABR7MNRV3PNCOKKK2HZAGMTPZ762PA5CNFSM4HWSFYA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXOJX6A#issuecomment-500997112>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABR7MNWVGIEPXSF6CHGZW3LPZ762PANCNFSM4HWSFYAQ>
.
|
@iamonuwa we won't be getting this in until that is verified cause this would endup going to our users if merged ! Would you be able to verify it & provide screenshots ? |
@thelostone-mc do we finally have a easy solution to test mails without them actually going out? Because right now we barely can test this at all. |
A screenshot would be great! |
It keeps failing for me
…On Fri, 14 Jun 2019, 11:48 Pixelant, ***@***.***> wrote:
A screenshot would be great!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4604?email_source=notifications&email_token=ABR7MNQDLK5E55UB4XIYJV3P2NZPDA5CNFSM4HWSFYA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXWN7WA#issuecomment-502063064>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABR7MNWZTILB45DKCN2L36LP2NZPDANCNFSM4HWSFYAQ>
.
|
@kuhnchris well if the needed data is present in db
Taking it a step further you could add ^ Those are the 2 ways I can think of ! I know it's cumbersome but we can't afford to merge this in without testing cc @danlipert / @octavioamu |
Totally agree. The only issue ATM is if the data is present |
I honestly don't think this is valuable - right now we do manual testing to see if the email is formatted correctly, etc by sending ourselves a test email before sending it out. There are usually issues that need to be addressed, and the timing of when the roundup is ready is not very stable. I'd like to see some consistency in preparing the content before we automate this. |
Maybe as a little background: I implemented MailDev a while ago to "locally send mails" without going out through a real mail server. Since we have a docker environment it should be pretty straight forward to include. (see https://danfarrelly.nyc/MailDev/) Maybe that's something to consider @danlipert ? |
Very cool! The manual test so much I dont worry about, but its the content being prepared on-time and accurately/bug-free. |
@iamonuwa please let us know if you can help wrap this up by Friday. Otherwise I'll need to bring it in internally. Thanks! |
You can make it internal |
@danlipert @octavioamu @thelostone-mc What exactly is missing here? Only manual testing or something else? |
I don't think this is valuable at all - right now the emails are visually
checked before going out for grammar issues, etc. and I don't know how we
can automate that easily.
…-Dan Lipert
On Thu, Aug 8, 2019 at 11:37 PM Rafał Kowalski ***@***.***> wrote:
@danlipert <https://github.com/danlipert> @octavioamu
<https://github.com/octavioamu> @thelostone-mc
<https://github.com/thelostone-mc> What exactly is missing here? Only
manual testing or something else?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4604?email_source=notifications&email_token=AAGUHEQ7K5Q6PEWI62WMCMTQDQVQ5A5CNFSM4HWSFYA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD332LZY#issuecomment-519546343>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGUHET7FA7R52S5SXNHZJTQDQVQ5ANCNFSM4HWSFYAQ>
.
|
for the weekly mails too? cause this is a mail in the style of "hey we found work for you". |
Description
Add send_weekly_recap to crontab
Refers/Fixes
Testing