Skip to content

feat(mywork): render issue summaries on todo cards + cap todos at 5 - #20

Merged
AndresL230 merged 1 commit into
mainfrom
feat/todo-summaries
Jul 6, 2026
Merged

feat(mywork): render issue summaries on todo cards + cap todos at 5#20
AndresL230 merged 1 commit into
mainfrom
feat/todo-summaries

Conversation

@AndresL230

Copy link
Copy Markdown
Contributor

Problem

The summarizer work (#18) joined issue_summaries into MyWorkTodo.summary server-side, but the todo card renderer (which landed via #17) never displayed the field — summaries reached the client and were silently dropped. (17 real AI issue summaries exist in prod right now; none render.)

The todo list was also uncapped, unlike previousActivity's 5-most-recent.

Fix

  • Web: todoCard renders the stored summary as escaped plain prose clamped to 2 lines, between the title row and the labels row. No markdown — the whole card is a single <a>, so nested links are off the table.
  • Worker: getMyWork caps todo at the 5 most recently updated open assigned issues, newest first — mirroring the PR cap. CLAUDE.md's My Work paragraph updated to match.

Tests

  • Worker: 7 assigned issues → exactly [7,6,5,4,3] (newest first, oldest cut).
  • Render: card with a summary shows it; card without one has no summary block.
  • Full suite 385 passing, typecheck + build clean.

🤖 Generated with Claude Code

The summarizer work (#18) plumbed issue_summaries through getMyWork
into MyWorkTodo.summary, but the todo card renderer (from #17) never
displayed it — summaries reached the client and were dropped on the
floor. The card now shows the stored summary as escaped plain prose
clamped to 2 lines (the whole card is one <a>, so no markdown links).

todo is also capped at the 5 most recently updated open assigned
issues, newest first — mirroring previousActivity's 5-most-recent cap.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 6, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@AndresL230, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 20e91323-0205-47dd-8f4b-c7b610537ae2

📥 Commits

Reviewing files that changed from the base of the PR and between 3c77033 and cf4240a.

📒 Files selected for processing (5)
  • CLAUDE.md
  • src/tools/mywork.ts
  • test/mywork.test.ts
  • test/render.mywork.test.ts
  • web/src/render.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/todo-summaries

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

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

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
canopy cf4240a Commit Preview URL

Branch Preview URL
Jul 06 2026, 05:17 AM

@AndresL230
AndresL230 merged commit afdf1aa into main Jul 6, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant