Skip to content

feat: Old Proposal Handler - Bounty #70 ($75)#89

Open
zhaog100 wants to merge 3 commits into
ubiquity-os:mainfrom
zhaog100:feat/old-proposal-handler
Open

feat: Old Proposal Handler - Bounty #70 ($75)#89
zhaog100 wants to merge 3 commits into
ubiquity-os:mainfrom
zhaog100:feat/old-proposal-handler

Conversation

@zhaog100
Copy link
Copy Markdown

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:

  1. Scan — Periodically scans repos for open issues matching proposal criteria
  2. Remind — Posts comments on stale proposals asking for updates
  3. Close — Auto-closes proposals with no response after warning period

Implementation

Repository: zhaog100/ubiquity-os-old-proposal-handler

  • TypeScript + Deno, follows UbiquityOS plugin template
  • Dual mode: event-driven (webhook) + CRON-based (daily scan)
  • Deno KV for state tracking
  • Structured metadata in comments for bot tracking
  • Full configuration via pluginSettingsSchema

Configuration

plugins:
  - uses:
    - plugin: old-proposal-handler
      with:
        staleThreshold: "30 days"
        warningPeriod: "7 days"
        proposalLabels: []
        targetRepos: ["ubiquity-os/plugins-wishlist"]
        closeOnExpiry: true

Files Changed

  • proposals/old-proposal-handler.md — Proposal document

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 12, 2026

Warning

Rate limit exceeded

@zhaog100 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 55 minutes and 12 seconds before requesting another review.

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 @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 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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 031693a4-5852-403e-8cfe-1de57c4ff1e1

📥 Commits

Reviewing files that changed from the base of the PR and between 7694148 and 61313d6.

📒 Files selected for processing (1)
  • proposals/old-proposal-handler.md
📝 Walkthrough

Walkthrough

Added 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 stale-proposal label with state tracked in Deno KV, and (3) closing proposals after a warning period without human activity. The implementation combines event-driven webhooks with daily CRON scans, includes configurable closure behavior, and provides example YAML configuration and implementation file responsibilities.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed Title accurately describes the main change: introducing the Old Proposal Handler feature for issue #70, clear and specific.
Description check ✅ Passed Description is detailed and directly related to the changeset, explaining the problem, solution, implementation approach, and configuration.
Linked Issues check ✅ Passed PR fulfills #70's requirements: provides automated mechanism to scan old proposals, remind maintainers, and auto-close after warning period.
Out of Scope Changes check ✅ Passed All changes are in-scope: single markdown proposal document introducing the Old Proposal Handler feature directly addresses #70.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5a52ee5c-ccfb-4d19-9562-f0af369ab53d

📥 Commits

Reviewing files that changed from the base of the PR and between edb3383 and 7694148.

📒 Files selected for processing (1)
  • proposals/old-proposal-handler.md

Comment thread proposals/old-proposal-handler.md Outdated
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.

Handling old proposals

1 participant