Add discord-collector in schedule yaml

[jonathanMLDev]

Summary

Discord is now on the Celery YAML schedule.

Changes

• config/boost_collector_schedule.yaml — Added discord group at 16:40 UTC with daily run_discord_activity_tracker (same pattern as slack).
• CHANGELOG.md — Noted the new schedule group under [Unreleased] → Changed.
• docs/GCP_Production_Checklist.md — Listed discord among Beat-scheduled groups; removed Discord from “Not on Beat yet”.

Verification

• Beat entry: boost-collector-group-discord-16-40 with schedule_kind=default, group_id=discord
• get_tasks_for_schedule('daily', group_id='discord') returns the Discord task
• 69/69 boost_collector_runner tests passed (project .venv)
• run_scheduled_collectors --schedule daily --group discord dispatches run_discord_activity_tracker (confirmed via manage.py logs and a mocked successful run)

Local note

A full unmocked run needs migrations (boost_collector_runner_collectorgrouprunstatus) and Discord env (DISCORD_USER_TOKEN, DISCORD_SERVER_ID, exporter). Without those, the collector fails after dispatch—as expected.

Related issue

• close Add Discord collector to Celery YAML schedule #251

Summary by CodeRabbit

• New Features

  • Discord activity tracking is now automatically collected on a daily schedule at 16:40 UTC.

• Documentation

  • Updated production deployment checklist to reflect Discord scheduling configuration.

[coderabbitai]

Warning

Review limit reached

@jonathanMLDev, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 25 minutes and 24 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b6744c7f-c6c4-4215-bbf2-f50f53031d9e

📥 Commits

Reviewing files that changed from the base of the PR and between 783581f and a8d52dc.

⛔ Files ignored due to path filters (2)

• requirements-dev.lock is excluded by !**/*.lock
• requirements.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• config/tests/test_health.py
• requirements.in

📝 Walkthrough

Walkthrough

This PR adds Discord collector scheduling to the Celery Beat infrastructure. The change introduces a new discord group to the YAML-driven schedule configured to run run_discord_activity_tracker daily at 16:40 UTC, alongside updates to the changelog and production checklist documenting the schedule addition.

Changes

Discord Celery Schedule Integration

Layer / File(s)	Summary
Discord schedule configuration and documentation config/boost_collector_schedule.yaml, CHANGELOG.md, docs/GCP_Production_Checklist.md	Adds discord group to boost collector schedule with default_time: "16:40" and daily run_discord_activity_tracker task, documents the scheduling change in changelog, and updates production checklist to reflect Discord is now configured in Beat rather than requiring manual execution.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• cppalliance/boost-data-collector#222: Shipped and validated the default Celery Beat schedule generation logic from the YAML configuration that this PR now extends with Discord support.

Suggested reviewers

• wpak-ai

Poem

🐰 A rabbit hops to say hooray!
Discord joins the schedule's way,
At sixteen-forty, UTC chime,
Activity tracked right on time! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main change: adding Discord collector to the schedule YAML configuration.
Description check	✅ Passed	The description covers the main changes, verification steps, and related issue, but omits most optional template sections (test plan details, specific checkboxes).
Linked Issues check	✅ Passed	All acceptance criteria from issue #251 are met: Discord group added to YAML, scheduled runs verified, tests passing, and Celery Beat entry auto-generated.
Out of Scope Changes check	✅ Passed	All changes directly support the linked issue objective of adding Discord to the Celery YAML schedule with no extraneous modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 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.

Inline comments:
In `@docs/GCP_Production_Checklist.md`:
- Line 44: Update the user-facing checklist text to consistently capitalize the
platform name: replace the token `github` in the line referencing
`config/boost_collector_schedule.yaml` with `GitHub` so the list reads `GitHub`,
`boost_library_docs`, `slack`, `discord`, `mailing_list`.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b8ea79bd-e75a-4db5-8006-0fe740f42c18

📥 Commits

Reviewing files that changed from the base of the PR and between c6be808 and 783581f.

📒 Files selected for processing (3)

• CHANGELOG.md
• config/boost_collector_schedule.yaml
• docs/GCP_Production_Checklist.md

[snowfox1003]

lgtm