feat: Old Proposal Handler - Bounty #70 ($75)#89
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 55 minutes and 12 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdded documentation for an automated stale proposal handler. The proposal outlines a three-stage lifecycle: (1) periodic repository scanning for stale proposals using configurable thresholds and optional labels, (2) posting reminder comments and applying a 🚥 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 |
Old Proposal Handler
Resolves #70
Problem
Maintainers rarely review old proposals on devpool.directory, and the team doesn't proactively handle them. This leads to a growing backlog of stale proposals.
Solution
A UbiquityOS plugin that automates stale proposal management:
Implementation
Repository: zhaog100/ubiquity-os-old-proposal-handler
pluginSettingsSchemaConfiguration
Files Changed
proposals/old-proposal-handler.md— Proposal document