CLI reference

fleet release

Name: Fleet
Author: Fleet

fleet release check <pr> [--label-approved <bool>] [--review-decision <decision>] [--project <slug>]

Provides the merge gate used by the release-manager agent. fleet release check <pr> exits 0 if the PR is mergeable and 1 if not, and always prints a JSON decision. The gate is satisfied when EITHER the GitHub reviewDecision is APPROVED, OR an approved label is set AND a pr_approved fabric event exists for the PR with no later pr_changes_requested.

This dual-signal design exists because Fleet agents share one GitHub identity, so gh pr review --approve fails on agent-authored PRs. The fabric event is the authoritative approval signal. The check is read-only and needs no license.

Flags

--label-approved <bool>	Whether GitHub reports the `approved` label set (true/false/yes/no/1/0)
--review-decision <value>	The GitHub `gh pr view --json reviewDecision` result; APPROVED is honored as a sufficient signal
--project <slug>	Override project scope (default: the cwd's .fleet/config.yaml)

Examples

Check whether PR 99 is mergeable

fleet release check 99
# {
#   "pr_number": 99,
#   "events_considered": 3,
#   "mergeable": true,
#   "reason": "approved",
#   "approved_by": "tech-lead"
# }

Pass the approval label and GitHub review decision explicitly

fleet release check 99 --label-approved true --review-decision APPROVED

Check a PR in a specific project

fleet release check 99 --project Feral-Intelligence/forge

Frequently asked questions

What fields does the JSON output contain?

pr_number (and/or pr), mergeable, reason, detail, approved_by, and events_considered. There is no verdict or label_approved field, and output is always JSON regardless of any flag.

Why a custom merge gate instead of branch protection?

Fleet agents share one GitHub identity and cannot approve their own PRs, so `gh pr review --approve` fails. The pr_approved fabric event from a reviewer agent is the authoritative signal; the gate reads both GitHub and fabric.

Related commands

fleet fabric →fleet log →fleet agent →

Run your first agent fleet

One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.

See how it works Install Fleet