Get merge readiness for a trail (repo_id addressing)
Authorizations
OAuth 2.0 authorization code flow.
Path Parameters
Repo id: placement ULID or public repo_
Trail number
Response
OK
Effective bypass policy for this response. When readiness is unavailable, nobody is a fail-closed fallback, not the saved repository setting; merge actions remain unavailable.
Third-party CI runs for headSha from the same read that evaluated the checks gate; Entire's own gate rollup is excluded. On an open native trail whose checks gate is pending, each required name with no report is also listed, with status queued and no started_at, whatever checks.availability says. Reported runs are meaningful only when checks.availability is available.
Provider conflict verdict for headSha; conflicting blocks mergeable independently of gates and CI evidence.
clean, conflicting, unknown Default for the merge request's deleteBranch option, i.e. the repository's delete-branch-on-merge setting; false means the setting is off. Null for a GitHub-backed repository, where entire-api never deletes the branch, and when readiness is unavailable.
Set when the forge's own branch rules (GitHub branch protection or rulesets) refuse the merge at headSha, independent of Entire's gates. Read under the GitHub App's credential, so it does not reflect a viewer's ability to bypass. Null when not blocked or unknown, and when GitHub waits only on Entire's own gates check run, which the gates already report.
A URL to the JSON Schema for this object.
"/api/v1/schemas/TrailMergeabilityResponse.json"