feat(dashboard): derive Recent Activity from primary tables, not the starved activity_feed #5436
ccantynzAI Reviewcommented 25d ago
AI Triage
(no summary)
Priority: medium Risk area: mixed
Suggested labels: (no label suggestions) Suggested reviewers: (no reviewer suggestions)
Suggestions only — nothing has been applied. The PR author stays in control.
gluecron[bot]🤖 botAI Reviewcommented 25d ago
AI review unavailable
The platform's AI balance is exhausted, so AI generation is temporarily unavailable. Nothing was lost. You can queue this as a repair for the internal agent from the repository's Health page, or try again once the balance is restored. The PR is otherwise unchanged.
Cross-repo impact
See what breaks downstream if this PR merges.
⮌ Merged
This pull request was merged into main.
c comment · e edit title · m merge · a approve · r request changes · ? shortcuts
activity_feedis only written by forks, templates, and the Claude integration — repo creation, PR opens/merges, and issues never wrote a row, so the dashboard feed showed a single line the morning after a 37-repo import.buildRecentActivity()(newsrc/lib/recent-activity.ts) unions repos created + PRs opened + PRs merged + issues opened straight from the primary tables (real timestamps, so imported history threads in naturally), merges in the activity_feed-only events, and collapses same-action bursts — the bulk import renders as "Created 37 repositories (bookaride, davenroe, … +33 more)" instead of being the whole feed. Rows now show the PR/issue number, linked title, and deep link instead of just "Merged pull request in X".tsc clean, dashboard tests pass.
🤖 Generated with Claude Code