-
Notifications
You must be signed in to change notification settings - Fork 181
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
Improve RCP communication by sending out reminders #3070
Conversation
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## stage #3070 +/- ##
==========================================
+ Coverage 96.40% 96.43% +0.03%
==========================================
Files 243 245 +2
Lines 55415 55727 +312
==========================================
+ Hits 53425 53743 +318
+ Misses 1990 1984 -6 ☔ View full report in Codecov by Sentry. |
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.
👍
This pull request is not passing all required checks. Please see this discussion for information on how to get all checks passing. Inconsistent checks can be manually retried. If a test absolutely can not pass for a good reason, please add a comment with an explanation to the PR. |
Reminder to set the |
Description
Sends a reminder 10 and 4 days before an RCP to milo dev.
Reminder RCP starts in 4 days from Fri, 25 Oct 2024 07:00:00 GMT to Sun, 27 Oct 2024 00:00:00 GMT. Merges to stage will be disabled beginning Wed, 23 Oct 2024 07:00:00 GMT.
My assumption: this can never trigger twice since this action runs once every 24h and we check if we are within a 24h timeframe, meaning we don't need to store any infos wether we already sent a message or not.
Resolves: MWPW-157289
Test URLs: