opencode-magi version
0.12.0
OpenCode version
1.18.9
Node.js version
v24.14.0
GitHub CLI version
2.87.3
Description
When a pull request leaves GitHub's merge queue because checks time out, opencode-magi ends the review as blocked instead of retrying the queue entry.
Pull request URL
yamada-ui/yamada-ui#7775
Command
/magi:review
Steps to Reproduce
- Configure
review.merge.queue as true.
- Run
/magi:review for an approved pull request.
- Let a required merge-queue check time out so GitHub removes the pull request with reason
checks_timed_out.
- Observe that the review ends as blocked with
PR left the merge queue before merging.
Operating System
Configuration
{
"review": {
"checks": {
"retryFailedJobs": 3
},
"merge": {
"queue": true
}
}
}
Logs or output
2026-07-28T23:37:53Z Added to merge queue
2026-07-28T23:48:40Z Removed from merge queue: checks_timed_out
2026-07-28T23:49:42Z Status: blocked
Error: PR left the merge queue before merging.
The retry logic only recognizes failed_checks; it should also retry entries removed with checks_timed_out, subject to the existing retry limit.
Do you know how to fix the issue?
Yes
Are you willing to participate in fixing this issue and create a pull request with the fix?
Yes
AI used
opencode-magi version
0.12.0
OpenCode version
1.18.9
Node.js version
v24.14.0
GitHub CLI version
2.87.3
Description
When a pull request leaves GitHub's merge queue because checks time out, opencode-magi ends the review as blocked instead of retrying the queue entry.
Pull request URL
yamada-ui/yamada-ui#7775
Command
/magi:review
Steps to Reproduce
review.merge.queueastrue./magi:reviewfor an approved pull request.checks_timed_out.PR left the merge queue before merging.Operating System
Configuration
{ "review": { "checks": { "retryFailedJobs": 3 }, "merge": { "queue": true } } }Logs or output
The retry logic only recognizes
failed_checks; it should also retry entries removed withchecks_timed_out, subject to the existing retry limit.Do you know how to fix the issue?
Yes
Are you willing to participate in fixing this issue and create a pull request with the fix?
Yes
AI used