Hack TK for Bloom

[DGoel1602]

Why

We need hack tk cause blooms tmr

What

Re-enabled Hack TK and changed constants for hack announcements

Checklist

CHANGE WEBHOOK FOR HACK ANNOUNCEMENT ENV 🙏

• Database: No schema changes, OR I ran pnpm db:generate and committed the generated files in packages/db/drizzle/
• Environment Variables: No environment variables changed, OR I have contacted the Development Lead to modify them on Coolify BEFORE merging.

Summary by CodeRabbit

• New Features
  • Hackathon event reminders are now actively scheduled and delivered through Discord.
• Updates
  • Hackathon reminder notifications now target the updated Discord role.
  • Refreshed the visual color of hackathon event reminder embeds for improved visibility.

[coderabbitai]

📝 Walkthrough

Walkthrough

Hackathon reminder notifications now use a new Discord role and embed color. The cron startup imports and schedules hackReminders, enabling the previously disabled hackathon reminder job.

Changes

Hackathon reminder activation

Layer / File(s)	Summary
Update hackathon notification settings apps/cron/src/crons/reminder.ts	The hackathon reminder role ID and embed color are updated.
Enable cron startup scheduling apps/cron/src/index.ts	hackReminders is imported and scheduled during cron startup.
Estimated code review effort: 2 (Simple)	~10 minutes

Possibly related PRs

• KnightHacks/forge#349: Also updates the cron reminder flow and hackathon reminder scheduling.

Suggested labels: CRON, Feature, Minor

Suggested reviewers: DVidal1205

🚥 Pre-merge checks | ✅ 4 | ❌ 4

❌ Failed checks (1 warning, 3 inconclusive)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title is related to the hack announcement changes, but it does not start with the required issue number in brackets.	Prefix the title with an issue number like "[#123]" and keep a concise description of the Hack TK changes.
No Hardcoded Secrets	❓ Inconclusive	Repository clone failed, so this custom check could not run with code access.	Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
Validated Env Access	❓ Inconclusive	Repository clone failed, so this custom check could not run with code access.	Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
No Typescript Escape Hatches	❓ Inconclusive	Repository clone failed, so this custom check could not run with code access.	Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bloom/reenable-hack-tk

Warning

Tools execution failed with the following error:

Failed to run tools: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

apps/cron/src/index.ts (1)

23-24: 📐 Maintainability & Code Quality | 🔵 Trivial

Track the post-hack cleanup TODO.

The comments acknowledge this is temporary tech debt ("This is terrible but can wait until after hack to change" / "Disable hacks after blooms over"). Consider creating a tracked issue so the cleanup isn't forgotten after the hackathon ends. Would you like me to draft one?

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/cron/src/index.ts` around lines 23 - 24, Create a tracked issue for the
temporary hack cleanup referenced by the comments near the cron initialization,
documenting the required refactor and the condition or timeframe for removing
the hacks after the blooms/hackathon period. Add the issue reference to the
relevant TODO comments so the follow-up work is discoverable.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@apps/cron/src/index.ts`:
- Around line 23-24: Create a tracked issue for the temporary hack cleanup
referenced by the comments near the cron initialization, documenting the
required refactor and the condition or timeframe for removing the hacks after
the blooms/hackathon period. Add the issue reference to the relevant TODO
comments so the follow-up work is discoverable.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: d47595e3-bfef-45e6-aa98-bcd7efbe2686

📥 Commits

Reviewing files that changed from the base of the PR and between e43730e and 83e47f5.

📒 Files selected for processing (2)

• apps/cron/src/crons/reminder.ts
• apps/cron/src/index.ts

[alexanderpaolini]

LGTM!