Skip to content

feat(maintainers): richer per-repo roster UI#230

Merged
MkDev11 merged 2 commits into
mainfrom
feat/maintainers-roster-ui
Jun 12, 2026
Merged

feat(maintainers): richer per-repo roster UI#230
MkDev11 merged 2 commits into
mainfrom
feat/maintainers-roster-ui

Conversation

@MkDev11

@MkDev11 MkDev11 commented Jun 12, 2026

Copy link
Copy Markdown
Owner

Follow-up to #229. Improves the By repo expanded roster (the list of a repo's maintainers).

Before

Every maintainer row repeated "registered miner" / "not a registered miner" — noisy on repos with many collaborators (e.g. we-promise/sure has 1 registered miner among 9 collaborators), and the list was flat.

After

  • Role pills — each maintainer's GitHub association (owner / member / collaborator) is now carried through the API and shown as a subtle pill — useful "who are these people" context.
  • One legend instead of per-row text✓ N / M registered miners — split this repo's X% maintainer cut, with the ✓ badge on registered rows. Removes the repeated status text.
  • De-emphasis — non-registered maintainers are dimmed and show for reward, so the reward-earning miners stand out.
  • Larger avatars, cleaner two-column (identity / reward) layout.

API adds association to RepoMaintainerEntry (no extra fetches — it was already in the mirror response, just dropped before).

tsc + eslint --max-warnings=0 clean.

Improve the By-repo expanded roster:
- carry each maintainer's GitHub association (owner/member/collaborator) through
  the API and show it as a subtle role pill — useful 'who are they' context
- replace the per-row 'registered miner / not a registered miner' text (noisy
  when a repo has many collaborators) with one legend line ('N / M registered
  miners — split this repo's X% cut') plus the ✓ badge on registered rows
- de-emphasize non-registered maintainers (dimmed) so the reward-earning ones
  stand out; show their reward as '—' instead of repeating the status
- larger avatars, cleaner two-column (identity / reward) layout
@coderabbitai

coderabbitai Bot commented Jun 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

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

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

⌛ 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 Plus

Run ID: 28997e14-475d-4b47-ba83-7b47c2f68fca

📥 Commits

Reviewing files that changed from the base of the PR and between 2392de2 and a062930.

📒 Files selected for processing (3)
  • src/app/api/maintainers/route.ts
  • src/app/maintainers/page.tsx
  • src/lib/api-types.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/maintainers-roster-ui

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.


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

…lumns

The per-repo breakdown under an expanded maintainer was cramped and unlabeled
('191 / 30d · 11h', '191 total', '35% cut' in their own grid). Re-lay it out on
the parent table's GRID so each repo's Shipping / All-time / Grade / τ-day sit
directly under those headers and visibly sum to the maintainer's aggregate row.
Mode + cut move to a subtext line under the repo name, median response time
becomes the shipping subtext, redundant 'total/τ-d/cut' suffixes drop (the
header labels them), and a thin connector tick marks the sub-rows.
@MkDev11 MkDev11 merged commit b3274e0 into main Jun 12, 2026
4 checks passed
@MkDev11 MkDev11 deleted the feat/maintainers-roster-ui branch June 12, 2026 03:47
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