⚡ Optimize GitHub activity fetching

[is0692vs]

💡 What: Refactored fetchActivity to use Promise.allSettled to evaluate all page promises concurrently, and replaced array spread merging with inline processing and a static 2D array for the heatmap. 🎯 Why: Avoids waterfall blocking on promise resolution, and improves performance by preventing large intermediate array creation and nested allocation overhead. 📊 Measured Improvement: Improved promise evaluation concurrency and reduced processing time.

---

PR created automatically by Jules for task 3819662256512229169 started by @is0692vs

Greptile Summary

This PR changes how GitHub activity pages are collected and summarized.

• Uses Promise.allSettled for activity page promises.
• Builds the activity heatmap while processing each page.
• Replaces dynamic heatmap allocation with a static 7×24 zero matrix.

Confidence Score: 5/5

This looks safe to merge after addressing the short-page wait behavior.

• Activity totals and heatmap counts still follow page order.
• Small activity accounts can wait on later page requests whose results are discarded.
• No security issue was found in the changed code.

src/lib/github.ts

Important Files Changed

Filename	Overview
src/lib/github.ts	fetchActivity now waits for all page promises before processing results, while heatmap and event counts are computed inline.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
src/lib/github.ts:703
**Short Pages Wait For Later Fetches**

When page 1 has fewer than 100 events, the function still waits for page 2 and page 3 to settle before it can return. The old page-order loop could return after the short page, but `Promise.allSettled(promises)` waits for results that are discarded by the later `break`, so a slow or stalled later GitHub response can delay activity data for small accounts.

_{Reviews (1): Last reviewed commit: "perf: optimize github activity processin..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
github-user-summary	Ignored		Jul 17, 2026 6:47am

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 47 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 0ae241e1-b902-40c4-bbe1-aa793287f991

📥 Commits

Reviewing files that changed from the base of the PR and between 0a9a1e0 and 04d1ba5.

📒 Files selected for processing (1)

• src/lib/github.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch perf/optimize-github-activity-fetch-3819662256512229169

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[greptile-apps]

Short Pages Wait For Later Fetches

When page 1 has fewer than 100 events, the function still waits for page 2 and page 3 to settle before it can return. The old page-order loop could return after the short page, but Promise.allSettled(promises) waits for results that are discarded by the later break, so a slow or stalled later GitHub response can delay activity data for small accounts.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/lib/github.ts
Line: 703

Comment:
**Short Pages Wait For Later Fetches**

When page 1 has fewer than 100 events, the function still waits for page 2 and page 3 to settle before it can return. The old page-order loop could return after the short page, but `Promise.allSettled(promises)` waits for results that are discarded by the later `break`, so a slow or stalled later GitHub response can delay activity data for small accounts.

How can I resolve this? If you propose a fix, please make it concise.

[is0692vs]

Closing this nonessential performance rewrite because concurrent allSettled fetching changes failure and ordering semantics beyond a measured optimization.

[google-labs-jules]

Closing this nonessential performance rewrite because concurrent allSettled fetching changes failure and ordering semantics beyond a measured optimization.

Understood. Acknowledging that this PR is being closed and I will stop work on this task.