Repository navigation
Keep a Stopped Group's Issue Out of the backlog-burndown Ranking - #3028
Merged
Merged
Conversation
An abandoned group whose cleanup fails is stopped and keeps its claim, so its issue returns to the ranking only once the maintainer's answer releases the group, rather than being ranked and claimed at once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ranking names a stopped group's issue as unranked until the maintainer's answer releases the group, so the rule binds where issues are ranked. A clean abandon releases its claim comment along with returning the issue. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Ranking exclusion now waits on the answer releasing the stopped group's claim, and that answer is written on the issue beside the question, so a later round can read both from durable state. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
Author
|
A recorded local strict-review pass covers head |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 33 minutes. View limit details
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 |
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Claim comments must be updated or released when a stopped issue resumes ranking.
1 open finding
What changed in this PR
Updates backlog-burndown to keep stopped groups out of ranking until maintainer resolution.
Changes:
- Clarifies cleanup and stopped-group behavior.
- Persists blocked-question answers.
- Regenerates distributed skill copies and source digest.
| File | Description |
|---|---|
.agents/skills/backlog-burndown/SKILL.md |
Canonical skill updates |
.github/skills/backlog-burndown/SKILL.md |
Generated copy |
.claude-plugin/fleet-skills/skills/backlog-burndown/SKILL.md |
Generated copy |
.claude-plugin/fleet-skills/.source-digests/backlog-burndown |
Updated source digest |
🧠 Review effort: Lite
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
The answer that releases a stopped group's claim is recorded in its claim comment before the issue is ranked again, so a kept branch's stale comment cannot collide with the re-formed group. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
Author
|
A recorded local strict-review pass covers head |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #3028 +/- ##
==========================================
Coverage ? 60.98%
==========================================
Files ? 17
Lines ? 9010
Branches ? 0
==========================================
Hits ? 5495
Misses ? 3515
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Owner
Author
|
@coderabbitai review |
|
ptr727
added a commit
that referenced
this pull request
Oct 15, 2026
…ng, and backlog-burndown Re-Dispatch Rules to Main (#3030) - #2997 adds an updater that keeps the coding-agent tools already installed on a host current, without installing a tool the maintainer has not chosen - #3017 brings the agent-safety READMEs up to the write guard's #3011 readings: `--admin` read inside a quoted `eval` argument, clustered and cut-short push options, `--branches` as `--all`, `refs/` pattern destinations, and a double-quoted list expansion as a directory or commit value failing closed - #3022 pairs a Copilot overview-table or `Review findings:` entry with a review thread by the file it names, replacing word overlap, compares the headline count against everything the round and the pull request account for, and makes `pr_review.py cleanup` read every page of the head pull requests, counting only this repository's own - #3018 has `backlog-burndown` name a new branch when an issue is dispatched again, name the open pull request a pushed branch still heads when cleanup reports it, and splits the long cleanup sentence - #3028 keeps an abandoned group's issue out of the `backlog-burndown` ranking while that group is stopped for the maintainer, and records the release on the claim comment - #3023 makes `gh-write-guard` read a `heads/` push destination as the branch git completes it to, read `--prune` beside a pattern, `:`, `--all`, or bare push as a delete of each branch matched, read `--mirror` as a force and a delete, and read the `@{push}` target against the configured remote names. A differential against the previous guard found no deny-to-allow flip - #3032 subtracts every thread id an open entry links, back-references included, from the earlier threads `pr_review.py`'s headline shortfall counts, so a back-referenced thread is no longer counted twice - #3035 covers the bootstrap upgrade handoff on Linux and Windows, the root and elevated skips included, and has `bootstrap.ps1` say when the agent tools report fails - #3037 makes `gh-write-guard` fail closed when a push target resolves but the remote names cannot be read After this merges, the host-safety installer payload changes, so the maintainer runs the installer after promotion. Fixes #3009 Fixes #2985 Fixes #3003 Fixes #2993 Fixes #3016 Fixes #3005 Fixes #3007 Fixes #2973 🤖 Generated with [Claude Code](https://claude.com/claude-code)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
backlog-burndown's "Grouping and File Claims" sent an abandoned group's issue straight back to the next round's ranking, while "Cleanup Is the Orchestrator's" stops an abandoned group whose branch carries commits develop lacks (or whose tree is dirty) for the maintainer, and a stopped group keeps its branch and its claim. The issue then ended up both ranked and claimed, and later rounds kept deferring it instead of reporting it as stopped..github/skills/and.claude-plugin/regenerated withscripts/build_dist.py.Closes on promotion: #3016
Local Review
Four recorded
local-strict-reviewpasses. Out-of-scope findings filed as #3026 and #3027. The oneintroducedfinding left open after the first push's edit budget (no sentence said the stopped group's claim comment is updated when the answer releases its claim) is fixed in e9c3e61, which also answers the Copilot thread raising it. Nointroducedfinding remains open.introduced, fixed:.agents/skills/backlog-burndown/SKILL.md"Ranking", claim comment not updated on release.Verification
python3 scripts/build_dist.py --check: current.python3 scripts/prose_lint.py --diff origin/develop: clean.python3 scripts/repo_gate.py: all checks ok.python3 spec/validate.py: OK.scripts/docker_lint.pymarkdownlint, cspell, editorconfig-checker: 0 issues.🤖 Generated with Claude Code