-
Notifications
You must be signed in to change notification settings - Fork 2
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
Member archive reminder cronjob #613
base: main
Are you sure you want to change the base?
Conversation
[diff-counting] Significant lines: 68. |
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 looks great, Patricia! The new cronjob follows the same style as the existing ones, and I like how you used the if checks to incorporate the new schedule with the preexisting ones.
I found that in checks, the one labeled ".github/..." fails. Github actions complains about "invalid workflow file", but I think it should be an easy fix.
member-archive-reminder: | ||
if: contains(github.event.schedule, '0 14 20 1,8 *') |
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.
I think these two lines should be indented one more, so that member-archive-reminder
is in jobs
, and if
is on the same indentation with runs-on
like the other two jobs.
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.
I think is a symptom of not having formatting on the YAML files. We shouldn't have to point these styling issues out :(
if: contains(github.event.schedule, '0 14 20 1,8 *') | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v2 |
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.
In Oscar's PR #607, he updated the workflows, so this should be changed to actions/checkout@v4
, along with lines 71 and 75. :)
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.
Overall, great work on this PR 👍 !! There is a message You have an error in your yaml syntax on line 66
in the github workflows.
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.
you've done an awesome job on this- it's lookin' good! However, I noticed in the cron configuration for 'profile-update-notifications' and 'tec-request-notification,' both jobs are triggered by the same cron schedule (0 23 * * MON), which may cause potential performance bottlenecks. 🐐
194bb2c
to
d624a08
Compare
Fyi this shouldn't be an issue unless we're saying that google/firebase and/or microsoft/github infra can't handle the load 😆 |
Summary
There will be a script made that archives members automatically each semester. This cronjob sends an email to the Ops Leads reminding them to upload the CSV from the returning members survey to archive members at the beginning of each semester.
Notion/Figma Link
https://www.notion.so/Member-archive-script-0540cb5e7d0349c4921f344b1875387e?pvs=4
Test Plan
Ran
yarn ts-node --transpile-only scripts/send-member-archive-reminder.ts
locally.Breaking Changes
Need to add an ops-leads collection with emails as the documents in the prod DB.