Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine

[Change Requests] - Schedule the work-package-deadlines cron

Open Beginner friendly
#4,429 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
36
Forks
9
Avg merge
4d 21h
Merged PRs (30d)
11

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
84/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.