merge_ready
Check if a pull request can merge by verifying review approval, CI status, and project guardrails, and get clear reasons for each blocker.
Instructions
May this pull request merge? One answer from the review gate, CI and the guardrails of
the project its ticket belongs to. pr is a PR URL or owner/repo#12. Returns ready
(true only when the PR is open, not a draft, the review gate approved its current head, CI
passed or the project has none, and no guardrail blocks), reasons (a sentence for each thing
holding the merge back; empty when ready), the head commit, and the review, ci and
guardrails answers. A bad reference, a PR no ticket has or a failed read comes back as
ready false with a reason. It changes nothing: it only answers; Tares's merge queue does the merging. project is accepted for
consistency with the other tools; the project comes from the pull request's ticket.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"pr": "<pr>"
},
"name": "merge_ready"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pr | Yes | ||
| project | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |