chore: weekly profile refresh#37
Conversation
|
Warning Review limit reached
More reviews will be available in 56 minutes and 13 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. 📝 WalkthroughWalkthroughThe "Recently shipped" section in ChangesProfile README Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
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 `@profile/README.md`:
- Line 37: The GitHub PR link in the network-website bullet point on line 37
currently points to the wrong repository slug. Change the URL in the link from
`https://github.com/greenpill-dev-guild/network/pull/10` to
`https://github.com/greenpill-dev-guild/network-website/pull/10` by updating the
repository path from `/network/` to `/network-website/` to match the correct
project name referenced in the project table.
🪄 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: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 4f01492d-01d4-4675-8ba8-af7266aec83d
📒 Files selected for processing (1)
profile/README.md
📜 Review details
⏰ Context from checks skipped due to timeout. (2)
- GitHub Check: Analyze (actions)
- GitHub Check: Analyze (javascript-typescript)
🧰 Additional context used
📓 Path-based instructions (4)
profile/README.md
📄 CodeRabbit inference engine (CLAUDE.md)
Use absolute GitHub URLs in
profile/README.mdfor links back into this repo
Files:
profile/README.md
**/*.md
📄 CodeRabbit inference engine (CLAUDE.md)
Link to the issue-creation flow in docs that ask someone to "open" an issue or RFC, not just the source template file
**/*.md: Do not introduce guild-wide Season framing in documentation
Do not describe the dev guild as the entire Greenpill Network in documentation
Avoid growth-hacking and trend-chasing voice in documentation: no FOMO, virality, leaderboards, streaks, or AI-first framing
Files:
profile/README.md
**/*.{md,yml,yaml}
📄 CodeRabbit inference engine (CLAUDE.md)
Search for and retire stale terms:
app.charmverse.io,greenpill.network/dev-guild,FOMO,virality,leaderboards,streaks,AI-first, former dev-guild PM URL, retired funded-work file names, old GitHub grant lifecycle labels, and retired Claude routine filenamesDo not reintroduce the former dev-guild PM URL or old migration language for project-management state
Files:
profile/README.md
{CONTRIBUTING.md,GOVERNANCE.md,SECURITY.md,SUPPORT.md,profile/README.md,.github/ISSUE_TEMPLATE/**,.github/PULL_REQUEST_TEMPLATE.md}
📄 CodeRabbit inference engine (AGENTS.md)
Treat contact emails, disclosure SLAs, payout timing, and governance claims as sensitive public commitments and do not change them casually
Files:
profile/README.md
Use the network-website repo slug (matches the project table) instead of the post-rename canonical `network` slug, so the profile is internally consistent. Both resolve; the rename redirect keeps the link working.
1 participant
Weekly auto-refresh of
profile/README.mdby theprofile-refreshroutine. Only the marker-bounded auto-managed sections may change; a human merges.What changed
Recently shipped — replaced the static "see releases" placeholder with the work that merged in the last 7 days (2026-06-15 → 2026-06-22). No tagged releases landed in the window, so these are notable merged PRs on each repo's active shipping branch (
main):/cookiesroute (green-goods#572, merged 2026-06-16).cookie-jarhad no merges into its shipping branch this week, so it is omitted.Now building — left unchanged this run. The Linear connector did not surface in this session, so I could not source live initiative/project state. Per the routine guardrail, I refreshed only the section I could source and left the Now-building block byte-identical rather than guess.
Sources & window
Scope
Only the content between the
recently-shippedmarkers changed. Thenow-buildingmarkers and every other line are byte-identical tomain. PR only — no direct push tomain.Generated by Claude Code