fix(triage): honor repo readiness gates and avoid ready-for-dev label loops
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, python
- Domain
- backend-api-design, devtools
Research direction
The fix is in skills/github-issue-triage/scripts/worker.py. Start by reading the existing triage prompt and logic. Understand how it currently decides to apply the ready-for-dev label. Then examine the target repository's readiness gate, likely .github/scripts/check_issue_readiness.py and its workflow. The goal is to make the extension call or respect that external gate before labeling. Run the existing contract tests with uv run pytest -q tests/test_github_triage_delivery.py. Done means the extension defers to the repo's rules, prevents label loops, and all tests pass.
Written by the indexing model from the issue text.
Description
Problem
The Extensions issue-triage agent repeatedly marked OpenHands/OpenHands#17510 ready-for-dev even though the repository's deterministic issue-readiness check rejected it: the issue is labeled bug, but its triage-generated Actual Behavior section contains only a screenshot/video placeholder, not the required embedded reproduction media. GitHub Actions removed the label; the triage automation reacted to that unlabeled event and added it back. Between 05:00 and 06:07 UTC on 2026-09-23 this one issue produced about 1,030 GitHub events and 190 triage runs, exhausting the OSS Canvas VM's memory.
The live OSS Canvas trigger now excludes ready-for-dev removals made by github-actions[bot] as an immediate circuit breaker. The Extensions automation still needs to make the right readiness decision itself, including on its initial opened or reopened event. Keep the fix in the existing issue-triage extension and reuse repository guidance/checks; do not introduce a second readiness mechanism.
Acceptance criteria
- Before applying
ready-for-dev, the agent checks applicable repository-specific issue readiness rules, including the authoritative.github/scripts/check_issue_readiness.pygate when present. It does not treat placeholder text as required evidence. - For a bug like OpenHands #17510 with no embedded reproduction media, triage may improve the issue and ask for the missing evidence, but leaves
ready-for-devabsent and does not repeatedly rewrite the managed section or comment. - A deterministic workflow's removal of
ready-for-devdoes not cause the triage automation to immediately reapply the label on an unchanged issue. A later substantive author edit or supplied evidence can be reconsidered. - A live or replayed before/after test shows no label loop and at most one triage conversation for an unchanged issue; an issue meeting the repository's criteria still becomes ready.
Observed event actors: all-hands-bot added the label; github-actions[bot] removed it. The current Extensions triage prompt is in skills/github-issue-triage/scripts/worker.py.
OpenHands AI triage
The following comments and acceptance criteria were added by the OpenHands AI agent.
Triage
The reported loop comes from a readiness disagreement, not from a missing trigger:
skills/github-issue-triage/scripts/worker.py vets an issue with its own prompt
criteria and then applies ready-for-dev, while a target repository such as
OpenHands/OpenHands evaluates the same label with its own deterministic gate
(.github/scripts/check_issue_readiness.py, invoked by
.github/workflows/issue-readiness-check.yml). That gate infers the issue type
from body sections and requires, for a bug, embedded screenshot/video media in
### Actual Behavior; a triage-written placeholder such as
_no reproduction media attached yet_ fails it. The workflow therefore removes
the label, the removal event re-triggers triage, and each cycle rewrites the
managed section and the readiness feedback comment, changing the next delivery
digest and re-dispatching - the ~1,030 events / 190 runs reported for
OpenHands/OpenHands#17510. This repository's own Ready-for-dev Label Policy
workflow only checks the applying actor's permission, so the fix has to live in
the extension and make the extension defer to the target repository's rules.
Bounded scope: keep the change inside skills/github-issue-triage
(worker.py, its prompt, SKILL.md/README.md, the catalog bundle, and the
contract tests) and make the run consult the target repository's existing
readiness rules before granting ready-for-dev, reuse that repository's
authoritative check instead of restating its rules, and remain idempotent on an
unchanged issue so a deterministic label removal cannot cause an immediate
reapplication.
Non-goals: no second readiness mechanism or re-derived copy of the repository's
criteria; no change to the target repository's readiness workflow or to the
host-side automation trigger / circuit breaker (owned outside this repository);
no new event trigger in the catalog manifest; no edits to unrelated skills,
plugins, or automations; no code implementation or PR review.
Acceptance Criteria
- Before applying
ready-for-dev, the triage run consults the target repository's own readiness rules and applies the label only when those rules pass, reusing the repository's authoritative gate when present (for example.github/scripts/check_issue_readiness.py) rather than re-deriving readiness inside the extension. - Readiness evidence is judged by what the repository gate accepts: descriptive or placeholder text such as
_no reproduction media attached yet_does not satisfy a bug report's required screenshot/video, and a body that would fail the gate is not marked ready. - When the repository gate fails, the run leaves
ready-for-devabsent while it may still record the managed triage section and/or a marked comment requesting the missing evidence; it never applies the label on its own criteria alone. - A re-run on an unchanged issue that already carries a current managed section or marked comment produces no new conversation, no section rewrite, and no label change, including when the only intervening event was a deterministic
ready-for-devremoval. - After a deterministic workflow removes
ready-for-devfrom an unchanged issue, the triage automation does not reapply it; a later substantive author edit, newly supplied evidence, or new human discussion re-enables reassessment and can make the issue ready. - An issue that does satisfy the repository gate (a bug with qualifying reproduction media, or an enhancement with a non-empty Desired Behavior and an Acceptance Criteria checklist) still receives
ready-for-devalong with its priority label. - Automated coverage reproduces the reported scenario: a test that fails before the change and asserts a single delivery for an unchanged issue whose gate fails, and asserts that
ready-for-devis not applied; the existing triage delivery contract tests continue to pass (for exampleuv run pytest -q tests/test_github_triage_delivery.py). - A rooted live or replayed before/after demonstration is provided showing no label loop and at most one triage conversation for an unchanged issue, and readiness for an issue that meets the criteria (the issue's fourth acceptance criterion).
- If the managed-section format or the delivery-digest inputs change,
TRIAGE_FORMAT_VERSIONis bumped so pre-existing marked sections are re-evaluated at most once and then stabilize, and legacy comment digests remain tolerated. - Because bundle files change, the automation's
setup.bundle.version(and the entryversion) inautomations/catalog/github-issue-triage/manifest.jsonare bumped and derived artifacts stay in sync (python3 scripts/sync_extensions.py --checkclean), andskills/github-issue-triage/SKILL.mdandREADME.mddescribe the readiness-gate behavior. - The change stays within the configured repository and issue scope using the existing fine-grained token: no new required permissions, no token value printed, and no mutation of repositories or issues outside scope.
- Dominant language
- Python
- Stars
- 184
- Forks
- 137
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 46
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenHands/extensions
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenHands/extensions#975 ·
Maintainers usually reply within 1 day
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OpenHands/extensions#973 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
OpenHands/extensions#970 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenHands/extensions#969 ·
Maintainers usually reply within 1 day
-
Add a `maven` skill: agents install Debian's `maven` package, which can't load plugins built for Java 17+Possibly taken @sumitvairagar claimed this 3 days ago. Openpriority:medium ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
OpenHands/extensions#963 ·
Maintainers usually reply within 1 day
All issues in OpenHands/extensions
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/datasets#9128 ·
Maintainers usually reply within 1 day
-
Function/dict state handlers can't supply provider-state injected values (`generate.provider_state`)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pact-foundation/pact-python#1789 ·
Maintainers usually reply within 9 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
juandresrodca/AdminForge#66 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
backend/local comp/tools P2 tool/terminal type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NousResearch/hermes-agent#158788 ·
Maintainers usually reply within 1 day