pr-pipeline: clear a feedback-not-landed escalation once the head moves and no lane thread is open
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 83/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- devtools
Research direction
Read .github/scripts/pr-merge/clear-escalations.mjs, especially the CHECKS table, and the related clear-escalations.test.mjs cases. Add the requested check using the escalation resume key and unresolved lane review threads, then run that test file. Done means the moved head with no open lane thread clears, while an unchanged head or an open lane thread keeps the escalation.
Written by the indexing model from the issue text.
Description
Problem
clear-escalations.mjs clears a pr-unblock escalation once its reason no longer holds, but its CHECKS table (.github/scripts/pr-merge/clear-escalations.mjs:120-132) covers only workflow-staged, unresolved-conflict, protected-path-conflict and feedback-protected-path. A feedback-not-landed escalation stays labeled after the cause is gone.
Example: #9965 escalated feedback-not-landed at resume key e5183af3; the head moved to 898665b3 with no unresolved review thread left, and ci-status stayed red only on the needs-human label until a person removed it.
Owner decision (2026-10-25)
A stop is worth a person only for security, intent, or a real charge. feedback-not-landed is none of those once the head has moved.
Fix
Add a feedback-not-landed entry to CHECKS in clear-escalations.mjs: the reason no longer holds when the head differs from the escalation's resume key and no review thread the lane replied to is left unresolved. Reuse the existing clearing path; add no second mechanism.
Done when
clear-escalations.test.mjscovers: head moved and no open lane thread clears; head unchanged keeps; an open lane thread keeps.
- Dominant language
- Shell
- Stars
- 22
- Forks
- 2
- Avg merge
- 2h 45m
- Merged PRs (30d)
- 940
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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 melodic-software/claude-code-plugins
-
admission-deferred priority: medium status: ready work-class: scoped
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
melodic-software/claude-code-plugins#10128 · 1 comment ·
Maintainers usually reply within 1 day
-
agent-ready priority: medium status: ready work-class: scoped
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
melodic-software/claude-code-plugins#9914 · 1 comment ·
Maintainers usually reply within 1 day
-
fix(harness-ops): bound the OTEL hot tier's total size, not only each filePossibly taken @melodic-automation-lanes claimed this today. Openagent-ready priority: medium status: ready work-class: scoped
Difficulty 2/5 1-2 days Newbie friendliness 78/100
melodic-software/claude-code-plugins#9865 · 3 comments ·
Maintainers usually reply within 1 day
-
priority: medium status: needs-decision work-class: scoped
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
melodic-software/claude-code-plugins#9855 · 5 comments ·
Maintainers usually reply within 1 day
-
priority: medium work-class: scoped
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melodic-software/claude-code-plugins#9842 · 5 comments ·
Maintainers usually reply within 1 day
All issues in melodic-software/claude-code-plugins
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
glossyio/traffic-monitor#256 ·
Maintainers usually reply within 1 day
-
source:reader type:content-error
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
stephrobert/blog-roadmap#121 ·
-
lesson-submission pending-review
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Ikalus1988/MisakaNet#3899 ·
Maintainers usually reply within 1 day
-
sync with NCO's changes
Difficulty 1/5 Under an hour Newbie friendliness 82/100