[Change Requests] - Schedule the work-package-deadlines cron
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions
- Domain
- ci-cd
Research direction
Start by locating the existing GitHub Actions workflow that curls /notifications/task-deadlines and review its notifications environment, backend URL, and notification secret usage. Add the matching work-package-deadlines workflow, set the UTC schedule for 5pm US Eastern with the daylight-saving choice documented, and confirm the endpoint, authorization, environment, and secrets match the acceptance criteria.
Written by the indexing model from the issue text.
Description
Description
Context
A GitHub Actions workflow triggers the existing daily notification by curling /notifications/task-deadlines on a cron with the shared secret. We need the same for the new work-package-deadlines endpoint. The time should be 5 pm eastern
Task
Add a GitHub Actions cron workflow that calls /notifications/work-package-deadlines with the notification secret, at the UTC time corresponding to 5pm US Eastern.
Acceptance Criteria
- A workflow curls the new endpoint with Authorization: ${{ secrets.NOTIFICATION_ENDPOINT_SECRET }} against ${{ secrets.BACKEND_URL }}, mirroring the existing task-deadlines workflow.
- The cron is set to the UTC time for 5pm US Eastern, and the daylight-saving approach is written down: a single fixed UTC time accepted as "5pm-ish year-round," or two seasonal entries / a documented adjustment.
- Uses the same notifications environment and secrets as the existing workflow.
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 14
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Northeastern-Electric-Racing/FinishLine
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
back-end draft
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
back-end draft
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
All issues in Northeastern-Electric-Racing/FinishLine
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100