fix(hygiene): sweep clears stale needs-triage + io-triage skips bot-authored issues - #21
Conversation
…uthored issues ticket-hygiene sweep now removes the needs-triage label from items that have become fully fielded (Area+Priority set) since the label was applied — it only ever added it before, so the Triage-health chart overcounted. Fetches issue labels in the board query and strips the stale label on a fully-fielded item. issue-ops-triage skips bot-authored issues (Renovate Dependency Dashboard edits errored triage at 0s, #17) and drops the dead ISSUE_OPS_PAT secret input (absent org/repo-wide; App token is the live path, reusable workflow marks gh_pat optional). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_beaa9d14-6396-445d-8cde-452d5c92eef0) |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 23 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 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 configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
Two follow-ups closing out the ticket-hygiene initiative.
1. Sweep clears stale
needs-triage(ticket-hygiene.yml)The daily sweep only ever added
needs-triage; it never removed it. After the 100% backfill, items that became fully fielded kept the stale label, so the Triage-health insight chart overcounted. The sweep now also fetches each board item's labels and, when an item is fully fielded (Area and Priority set) but still carriesneeds-triage, strips the label. Reported in the run summary ascleared the stale label from N now-fully-fielded item(s).2. io-triage skips bot-authored issues + drops dead PAT (issue-ops-triage.yml) — closes #17
issue-ops-triageand errored at 0s. Job now guarded withgithub.event.issue.user.type != 'Bot'.gh_pat: ${{ secrets.ISSUE_OPS_PAT }}input —ISSUE_OPS_PATis absent org/repo-wide,IO_USE_APP=trueuses the App token, and the reusableio-triage.ymlmarksgh_patrequired: falsewith anapptoken || gh_pat || github.tokencascade (verified at the pinned SHA).Safety
jqequality checks / a fixed bashcaseallow-list — never interpolated into a query or shell command.updateProjectV2ItemFieldValue/ label edits use parameterized-Fvariables and the SHA-pinned App token.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Note
Low Risk
Workflow-only changes to label hygiene and triage guards; no application runtime or auth logic beyond existing GitHub App tokens.
Overview
Issue-ops triage no longer runs on bot-authored issues (
github.event.issue.user.type != 'Bot'), avoiding failures when Renovate’s Dependency Dashboard fireseditedevents (#17). The unusedgh_pat/ISSUE_OPS_PATsecret input was removed in favor of the existing App-token path in the reusable workflow.The daily ticket-hygiene sweep now loads issue labels and treats fully fielded board items that still have
needs-triageas candidates for cleanup. For those items it removes the stale label (instead of only ever adding it), and the step summary reports how many were cleared so Triage-health metrics stop overcounting.Reviewed by Cursor Bugbot for commit 0c15182. Configure here.
Summary by cubic
Improves ticket hygiene automation: the daily sweep now clears stale
needs-triagelabels once items are fully fielded, andissue-ops-triageskips bot-authored issues to avoid noisy failures. Also removes the unusedgh_patinput in favor of the App token.needs-triagewhen both Area and Priority are set; adds the count to the run summary.issue-ops-triageruns only when the issue author is not aBot, preventing Renovate edit failures; closes [Bug] io-triage fails on Renovate Dependency Dashboard edits (+ dead ISSUE_OPS_PAT input) #17.gh_patsecret input; uses the App token viaIO_USE_APP=trueand the reusableio-triage.ymltoken cascade.Written for commit 0c15182. Summary will update on new commits.