Synced from Hive. This page is pulled from hivecommons/hive@v5 during the docs build. Edit the canonical source in the Hive repository.

Maintainer commands

Maintainers steer Hive by commenting commands on issues and pull requests. Hive does not depend on a webhook for the state-changing /hive issue commands: the spoke scans comments during its issue un-park sweep, which runs about every five minutes. The /hive help, /fixed, /reopen, label-helper, and assignment helper commands are GitHub Actions conveniences that answer new comments as soon as Actions schedules the workflow.

Canonical v5 URL: https://github.com/hivecommons/hive/blob/v5/src/docs/maintainer-commands.md

Command table

CommandWhat it doesWho may use itWhere it worksPickup speedLabels changed
/hive approveAccepts the recommendation already written on a parked issue.Human commenter with write, maintain, or admin repository permission.Open issues carrying needs-human or stage/045-needs-decision (or the retired needs-decision / needs-direction / a pre-045 stage/085-needs-decision, until migrated). On an open pull request the command gets one acknowledgement or explanation reply and changes no labels (see PR approval command feedback).Next un-park sweep, normally within 5 minutes.Removes stage/045-needs-decision (and the retired spellings) when present; adds approved-direction; removes needs-human whoever added it — your approval is the human input the label asked for (#13075, docs#419); the reply names who had added it. Never removes hold: add hold to keep agents off an issue through a decision.
/hive decision <text>Gives explicit direction for a parked issue.Human commenter with write, maintain, or admin repository permission.Open issues carrying needs-human or stage/045-needs-decision (or the retired needs-decision / needs-direction / a pre-045 stage/085-needs-decision, until migrated); pull requests are ignored.Next un-park sweep, normally within 5 minutes.Removes stage/045-needs-decision (and the retired spellings) when present; adds approved-direction; removes needs-human whoever added it — your decision is the human input the label asked for, and left in place it would re-derive 045 two minutes later (#13075, docs#419); the reply names who had added it. Never removes hold: add hold to keep agents off an issue through a decision. An agent’s later re-park on 085 is refused while approved-direction is present and the recorded decision text is unchanged; an agent’s later needs-human (the remaining work is human-only) keeps approved-direction and holds the issue out of the pipeline instead of re-deriving stage/045-needs-decision (#16579). A newer /hive decision with different text means direction is changing: an agent’s park goes through, the stale approved-direction is cleared, and the issue waits at stage/045-needs-decision until the sweep applies the new decision.
/hive decision proceed — <gap>Confirms a feature request parked by the prior-art gate is a real gap.The issue author, or a human commenter with write, maintain, or admin.Open issues carrying stage/017-possible-existing below a <!-- hive:prior-art-gate --> comment.Next un-park sweep.Removes stage/017-possible-existing, appends a Scope vs existing section with <gap> to the issue body, records the un-park so the issue re-derives stage/010-actionable (#13575).
/hive decision existsAgrees the request already exists.Same as above.Same as above.Next un-park sweep.Adds already-exists, closes the issue not_planned, replies with a pointer at the quoted findings. Reopen the issue to continue; the gate does not ask again.
/hive helpPosts this command list. On parked issues it also repeats the issue-specific approve/decision options.Any human commenter with at least triage repository permission for the on-demand workflow; the sweep path on parked issues requires write, maintain, or admin.Any open issue or pull request.GitHub Actions on the new comment; if Actions is unavailable on a parked issue, the next un-park sweep can also answer.None.
/hive ack [episode]Acknowledges an attention episode on the item: you have seen it, so reminders for it stop. Acknowledgement is not approval. See Attention ack and snooze.The episode’s named responsible person, or a human with write, maintain, or admin repository permission. Anyone else is ignored in silence.Open issues and pull requests with an unresolved attention episode, on a repository whose github.attention.admitter is this hive.Next un-park sweep, normally within 5 minutes.None. Never releases a security, merge or review hold and never opens a merge gate.
/hive snooze <duration> [episode]Pauses reminders for an attention episode until the duration elapses (90m, 4h, 2d, 1w; 1m to 30d).Same as /hive ack.Same as /hive ack.Next un-park sweep, normally within 5 minutes.None. A snooze releases no hold.
/fixedConfirms that an open issue’s fix is verified — or that what a parked issue waited on was done, in or outside the repository — and closes it as completed. Alias: /close. Plain-language confirmations such as “yes, this has been fixed” are accepted only when Hive is already waiting for reporter confirmation.The issue reporter, or a human with write, maintain, or admin repository permission. On a parked issue (stage/045-needs-decision, needs-human, or a retired park spelling) the un-park sweep honours it from a human with write, maintain, or admin permission.Open issues only, not pull requests.GitHub Actions on the new comment where the repository runs the /fixed workflow; on parked issues, the next un-park sweep, normally within 5 minutes (dibs#459).Closes the issue as completed. The workflow adds hive: reporter-confirmed and removes hive/likely-done and needs-reporter-confirmation when present. On a parked issue the sweep removes needs-human and the retired park spellings, the stage engine strips stage/*, and Hive posts one acknowledgement; hold is never touched.
/reopenReopens a closed issue that was closed too early.The issue reporter, or a human with write, maintain, or admin repository permission.Closed issues only, not pull requests.GitHub Actions on the new comment.Removes needs-reporter-confirmation when present. The reopen sticks: close-on-merge does not close the issue again for a PR that merged before the reopen, whether Hive (<!-- hive-close-on-merge --> comment) or GitHub’s closing keyword closed it; Hive records the latter with a <!-- hive-reopened-after-merge pr=<pr> --> comment. A later PR can still close it.
/help-wantedAdds the help wanted label.Any non-bot commenter accepted by the label-helper workflow.Issues and pull requests.GitHub Actions on the new comment.Adds help wanted.
/good-first-issueAdds the good first issue label.Any non-bot commenter accepted by the label-helper workflow.Issues and pull requests.GitHub Actions on the new comment.Adds good first issue.
/hacktober-festAdds the hacktober-fest label.Any non-bot commenter accepted by the label-helper workflow.Issues and pull requests.GitHub Actions on the new comment.Adds hacktober-fest.
/kind <kind>Validates or requests a kind label. The Hive label helper reports invalid values and lists the accepted kind names; repositories may also have Prow or other automation that applies valid labels.Any non-bot commenter accepted by the label-helper workflow, subject to any repository label automation that applies the label.Issues and pull requests.GitHub Actions on the new comment.The helper itself changes no labels for valid /kind comments; companion repository automation may add kind/<kind> or equivalent labels.
/area <area>Validates or requests an area label. The Hive label helper reports invalid values and lists the accepted area names; repositories may also have Prow or other automation that applies valid labels.Any non-bot commenter accepted by the label-helper workflow, subject to any repository label automation that applies the label.Issues and pull requests.GitHub Actions on the new comment.The helper itself changes no labels for valid /area comments; companion repository automation may add area/<area> or equivalent labels.
/assignAssigns the commenter where the repository’s assignment automation supports slash-command assignment. The Hive assignment helper deliberately ignores the exact command because Prow handles it, but it points natural-language assignment requests to this command.Repository assignment automation decides; the helper response is available to non-bot issue commenters.Issues.Repository assignment automation or GitHub Actions helper on the new comment.Assignment state changes, not labels.
/unassignRemoves the commenter’s assignment where the repository’s assignment automation supports it.Repository assignment automation decides; the helper response is available to non-bot issue commenters.Issues.Repository assignment automation or GitHub Actions helper on the new comment.Assignment state changes, not labels.
/claimSays “I am working this issue”: a contributor-lane lease on the issue is released and its relay task yanked, no new contributor claim is accepted on it and the hive will not adopt a contributor PR for it unless you release it (#18899). It is read from the forge by the claim gate, not parsed by a sweep and not written to the ledger by itself: to register a claim in the ledger use the dashboard or hivectl claim owner/repo#N.A commenter with author association OWNER, MEMBER or COLLABORATOR; bots and the contributor holding the lease are ignored.Open issues.The contributor claim’s next lease renewal or the five-minute claim release tick.Applies hive/claimed-by-human and stage/020-claimed when the claim is recorded in the ledger.
/unclaimWithdraws your own /claim comment.The same commenter.Open issues.Same as /claim.None.

Claiming an issue

A person’s claim outranks the contributor lane. Any of these on an open issue, made by an owner or maintainer (a person with write, maintain or admin repository permission, never a bot or the hive’s own App), counts as a human claim even though none of them goes through the claim ledger (#18899, child of #18890):

  • Assigning the issue. This is what an operator’s dispatcher does: gh issue edit --add-assignee plus a plain “Claimed; fix in progress.” comment. The assignment is the claim; the comment is courtesy. An assignee who is the contributor holding the lease is not a claim against that contributor (a maintainer handing the issue to them).
  • A /claim comment (or a plain comment opening with “Claimed”) from an OWNER, MEMBER or COLLABORATOR, until the same person comments /unclaim.
  • Applying hive/claimed-by-human by hand. The same label applied by the hive is the ledger speaking and is not a claim.

What a human claim does: a live contributor lease on the issue is released (release reason human claim: assigned by <login>, human claim: /claim comment by <login> or human claim: hive/claimed-by-human label by <login>), its relay task is yanked so the lane moves on, and the person is recorded as the ledger claim holder. While it stands a contributor’s fresh claim and renewal are refused, and the hive does not adopt a contributor PR whose Fixes #N names the issue (the tracker row reads “an owner or maintainer has claimed the issue”). It lifts when the person unassigns, removes the label or comments /unclaim. The supported way to register a claim in the ledger is the dashboard or hivectl claim owner/repo#N; the three forge signals above are detected, not ledger entries of their own.

Eligibility rules

Hive-authored issues normally arrive actionable rather than parked when the question is only an engineering choice (sequencing, naming, numbering, config shape, scope, or approach A vs B). With project.agent_issue_decision_policy: resolve (the default), the relay downgrades those attempted parks and records Decision taken by hive: …; maintainers can still override with /hive hold or needs-human. Parked Hive-authored issues should include Risk: <category> for the reason a person is required.

The un-park sweep only honors /hive approve, /hive decision <text>, /fixed (alias /close), and the sweep fallback for /hive help when the command is the first non-empty line of the comment, outside quoted text and fenced code. The comment must be newer than seven days, unedited, authored by a human rather than the hive or another bot, and posted by someone who currently has write, maintain, or admin permission on the repository. A /hive decision must include non-empty instructions.

On an issue, a first line of Decision: <text> (or Decision (owner): <text>) is read as /hive decision <text>, under the same permission, freshness and unedited rules; the lines after it are kept as part of the decision. A first line that names a decision without recording one (Decision: with no text, decide ..., option 1, or a bare option letter such as B) un-parks nothing and gets a reply telling the commenter to use /hive decision <text>. PRs keep the strict /hive decision shape.

The on-demand /hive help workflow uses the same first-line command shape, is ignored for bot comments, and allows triage, write, maintain, or admin because it only posts reference text and changes no labels.

PRs use GitHub’s native review signal instead of /hive approve; a /hive approve comment on a PR is acknowledged or explained but changes no labels and is not consumed by any merge lane (see PR approval command feedback). When the swarm has not approved the current head because it returned requires_human, a human who is trusted to queue merges can submit a normal GitHub Approve review on that exact head SHA to clear stage/085-needs-decision for any author kind/lane. No special review body is required; the queued human-merge lane’s Approved by @... for Hive auto-merge on green CI. body remains specific to that queue flow. A swarm changes_requested or reject verdict is not overridden by a human approval; the head must be fixed or merged manually.

For a PR whose closing claims were superseded by another merged PR, a trusted maintainer with repository write access can reply /hive decision reject or /hive decision close superseded by #N. Hive rechecks that the claimed issues are closed and a different merged PR closed them; an explicit #N must match that closer. It comments and closes the PR with hive/superseded, including PRs opened by contributors, without pushing to their branches. Hold and do-not-merge gates still prevent the close. When nothing supersedes the PR, a bare reject keeps its ordinary meaning (changes requested, nudging the author), while an explicit close superseded by #N is answered with why the PR stays open. The sweep’s hive/supersession-pending cause label keeps the unresolved decision at 085 through CI or rebase failures; reopening the issue, rewriting the claim, or choosing hive/keep-open clears the sweep’s park on its next pass.

On a hive-authored PR (author/hive) parked at stage/085-needs-decision the same trusted human has a second lever (#13041): a GitHub changes requested review on the current head, or a /hive decision &lt;what to change&gt; comment, moves the PR to stage/070-fixing and kicks the author agent once per head with the review/decision text quoted verbatim plus the swarm’s outstanding findings; the swarm verdict for that head is superseded, and the new head the agent pushes gets the normal swarm re-review. One kick per (head, review/comment): a second sweep over the same head does not re-kick, a dismissed review or a later approval by the same reviewer clears it, and a changes-requested review left on an older head is outdated. The fix kick is delivered ahead of the governor’s own kick to the same agent in that eval cycle, so it does not time out behind routine queue work; a kick that still cannot be sent is logged as review swarm kick not delivered with the PR and audited as review_kick_undelivered, and the planner re-plans it next cycle. The whole comment after /hive decision is the instruction — numbered points on the lines below the command are kept and quoted verbatim — and the decision on the current head outranks the swarm’s decision-requested verdict on that head, so the stage moves in the same pass as the acknowledgement rather than waiting on a re-review. A /hive decision whose first word is approve, approved, or lgtm (a trailing comma or period is fine) is recorded as approval; the rest of the comment is retained as its rationale. A bare yes approves too, but yes, but … is a conditional answer and is routed as an instruction. To request changes, start with the instruction (e.g. /hive decision change the PR body to Refs #123). No fix is kicked for an approval, requires_human is released for that head and the PR follows the normal merge path. An acknowledged decision whose record did not survive a pod restart is rebuilt from the comment thread; a decision answered for an older head is left alone (#14679). The sweep also reads /hive decision at stage/070-fixing: approve the current head after a body or metadata fix to release a standing request without pushing a cosmetic commit. A later trusted GitHub APPROVED review on the same head also supersedes the recorded request; an older approval does not. If that review is later dismissed, or the reviewer asks for changes again on the same head, the review-backed approval is dropped and the earlier instruction stands again — a /hive decision approve comment is durable and is not. Issue-link repair preserves edited Refs bodies and PRs with a recorded decision, so it cannot restore auto-close over the owner’s direction. The 085 entry comment names both actions. The commenter must hold write or better on the repo and be in the hive’s trusted-merger set (the bar a human approval already meets). /hive decision on a PR the hive did not open, or /hive approve / /hive help on any PR, gets one reply naming the review-side equivalents instead of silence; the hive never pushes to a PR it did not open.

/fixed and /reopen are intentionally narrower: they work for the issue’s own reporter or for write/maintain/admin collaborators. /fixed plain prose is only meaningful when Hive has already asked whether a merged referenced fix can close the issue; an explicit /fixed works on any open issue. Ambiguous prose with negation or remaining-work language asks the commenter to use /fixed instead of closing. On a parked issue — many park for an action a person must take outside the repository — the un-park sweep itself honours a maintainer’s /fixed, so a repository without the /fixed workflow still gets the close, the label clean-up and one acknowledgement.

Attention ack and snooze

Attention episodes (#16270) ask one named person to act on one condition. /hive ack and /hive snooze <duration> let that person, or a maintainer, answer the ask without resolving it (#16359):

  • The command must be the first non-empty line of a recent, unedited comment by a human, outside quotes and fences — the same rules as the un-park commands. Only the hive named by github.attention.admitter for the repository answers, so a fleet replies once.
  • Without an [episode] argument the command applies to every unresolved episode on the item that you may act on. To target one, pass the key prefix shown in the item’s attention status section, e.g. /hive ack 3f9a0c12b7de.
  • /hive ack records who acknowledged and when; /hive snooze records who snoozed and until when. Both are stored on the episode in the attention ledger, refresh the status section, and get one reply.
  • Acknowledgement is not approval. Neither command adds or removes a label, releases a security, merge or review hold, or opens a merge gate. To release a hold use the lever the hold names (for example a trusted merger’s GitHub Approve review); to resolve the episode, fix the condition — it resolves when Hive no longer observes it.
  • A caller who is neither the episode’s responsible person nor a maintainer is ignored in silence and nothing is recorded. A malformed duration from an eligible caller gets a reply explaining the accepted forms.

Prose replies on parked issues

Plain approvals such as “approved”, “go ahead”, “sounds good”, or “ship it” do not un-park an issue. When an eligible maintainer writes prose that looks like assent, Hive posts a hint asking for /hive approve or /hive decision <text> and leaves all labels unchanged. This avoids turning casual agreement into a state-changing instruction.

Model-defined replies

A repository bound to a workflow model may declare its own human-gate verbs per state (replies). On a parked issue in such a repository, /hive <verb> with one of those verbs — multi-word verbs are fine, case does not matter — is accepted like /hive decision: the parking labels are cleared, approved-direction is added, the label the model maps to the verb’s target state is applied when it declares one, and the reply comment says what the model did with the verb. Any text after the verb is kept as the decision. The Activity Monitor’s human-gate pill offers the same verbs after the built-in ones. Repositories without a binding, and pull requests, behave exactly as described above; the model’s verbs are not recognised there.

Idempotency markers

Hive marks its standing parked-issue notice with <!-- hive:unpark-notice:9879 --> and edits that comment in place when the issue options change. Each answer to a specific maintainer comment is marked with <!-- hive:unpark-reply:9879 id=<comment-id> -->. The sweep and the on-demand /hive help workflow both check that per-comment marker before posting, so reruns and sweep/action overlap do not duplicate replies or repeat label changes.

The /fixed workflow uses the reporter-confirmation labels and comments described above. While Hive waits, issues carry needs-reporter-confirmation (and may also carry needs-human when the reporter is a maintainer). /reopen, label-helper, and assignment-helper commands are single-comment workflows; repeat comments can repeat their documented action.

However an issue closes — /fixed, a merged PR’s Fixes #N, or by hand — Hive clears the stage labels it left on it: the closed-issue sweep (every 10 minutes) strips stage/* and a Hive-added needs-human from recently closed issues, so a closed issue never sits in the dashboard tracker as needing a decision (homebrew-hive#127). A person’s needs-human and any hold stay.

The hive/selfreport label

Issues labelled hive/selfreport were filed by a hive about itself ([selfreport] <class>: …, see fleet-report.md). Each affected hive is listed in the Affected hives (N) block of the body; hives that hit the same condition add themselves rather than filing duplicates, so the body block is the fleet-wide tally. Hives post a “cleared on <hive>” comment when the condition stops — at most once per hive per 24h for a flapping condition, and never under a closed issue (the hive reads the state first and records the close) — but never close these issues; close them when the fix has rolled out. Closing a self-report silences its reporter for that fingerprint for as long as the reporter keeps observing the condition (the 7-day cooldown runs from the last observation, not the close), so an old build that still carries the bug does not re-file daily after an “already fixed on v5” close. A hive that was quiet about it for 7 days and then sees it again files a new issue, so /reopen the original instead if the fix did not hold.

Label-driven repositories

Some repositories accept and park issues entirely with labels and their own lifecycle bot (for example needs-triage → triage/accepted, with the bot removing needs-human). Clearing those labels from Hive would fight that workflow, so an operator can opt a repository in per repo — in the config file or from the dashboard (Settings → Repos → “Label-driven approvals (Prow-style)”, write or owner role):

project:
  label_driven_approval_labels: [triage/accepted]   # default
  label_driven_trust_org_members: true              # default (Prow's rule)
  label_driven_trusted_bots: [hivecommons-prow[bot]]   # default
  # label_driven_supersede_park_actors: ["github-actions[bot]"]   # default empty
  repo_policies:
    - repo: projectbluefin/common
      label_driven: true
      # label_driven_approval_labels: [accepted]    # optional per-repo list
      # label_driven_supersede_park_actors: ["github-actions[bot]"]   # optional per-repo list

This is strictly opt-in (hivecommons/hive#11313). Repositories without label_driven: true behave exactly as described in the sections above; the only global changes are that an issues label webhook lets the un-park sweep run early, and once-only reply markers are trusted only when the hive itself wrote them.

On an opted-in repository the un-park sweep:

  • posts no “What to reply” notice (<!-- hive:unpark-notice:9879 -->) and no hint for prose assent;
  • treats a trusted addition of an approval label as approval: it removes the park labels Hive itself added, adds approved-direction, and replies once per acceptance (<!-- hive:label-approval:11313 event=N -->). No /hive comment is needed;
  • answers /hive approve and /hive decision <text> the same way (Hive-added park labels only), and also accepts them from collaborators with the GitHub triage role; /hive help gets a one-line reply pointing at the labels;
  • never removes a park label a person added, nor hold / do-not-merge. When one of those is present the issue stays parked and Hive posts one “accepted, but still held by …” note naming the labels.

Lifecycle bots that park every new issue

Some repositories run a lifecycle bot that adds needs-human to every new issue and never removes it; Hive’s rule of removing only its own park labels would then keep an accepted issue parked forever (#13605). List that bot in label_driven_supersede_park_actors (project-wide, or per repo under repo_policies[]) and a trusted acceptance added after the bot’s park label supersedes it: Hive removes the label, says so in the release comment (“needs-human (added by @github-actions[bot]), superseded by the acceptance as this repository’s configuration allows”), and releases the issue. A park label added by a person, by an unlisted bot, or by a listed bot after the acceptance still blocks exactly as before, and hold / do-not-merge are never superseded. The list is empty by default.

Parked issues are still filtered from enumeration, and Hive may still add stage/045-needs-decision with a comment asking the question. (Owner decision, 2026-10-17: issues park at stage/045-needs-decision; stage/085-needs-decision is PR-only. The un-park sweep still clears a pre-045 085 from an issue.)

Who may apply the approval label

Only the actor of the most recent labeled event for the label is checked (removing and re-adding re-evaluates the newest event). Trusted, in order:

  1. a bot in label_driven_trusted_bots (Prow command bots relaying /triage accepted). The default list is only hivecommons-prow[bot]. github-actions[bot] is not trusted by default because it is the shared identity of every workflow in the repo; if your Prow emulation runs as github-actions[bot], add it explicitly per deployment;
  2. a collaborator whose GitHub role_name is triage, write, maintain or admin (custom roles that build on triage count as triage);
  3. a public member of the repository’s owning org, when label_driven_trust_org_members is on (default).

Anything else — an untrusted person, an unlisted bot, a label Hive applied itself, or a timeline that could not be read — is not approval; the sweep fails closed and logs once.

What each label does on a label-driven repository

Label approval layers on top of the existing label paths rather than replacing them; the table states every effect in one place.

LabelUn-park sweep (label-driven repo)PR self-authorization sign-offReporter-trust admission (issue_filter.reporter_trust)
triage/accepted (or configured approval label) applied by a trusted actorReleases the issue: Hive-added stage/045-needs-decision (and retired spellings) removed, approved-direction added, one reply; needs-human is kept even when Hive added it (only the /hive commands lift a Hive-added one)Counts as human sign-off, like approved-directionUnchanged: still one of the labels that admits an untrusted reporter’s issue if listed in untrusted_require_labels
same label applied by an untrusted actor / unreadable timelineNo effect (fail closed)Not sign-offUnchanged
approved-directionIssue is not parkedHuman sign-off (unchanged)n/a
stage/045-needs-decision added by HiveRemoved on label approval or /hive approveParked → no sign-offn/a
stage/045-needs-decision added by a personKept; issue stays parked, Hive posts one “still held” noteParked → no sign-offn/a
needs-human added by HiveRemoved on /hive approve / /hive decision / /fixed — the maintainer’s answer to the hive’s own ask (#13075); kept on label approval; removed when the issue closesParked → no sign-offn/a
needs-human added by a bot listed in label_driven_supersede_park_actors before the acceptance (#13605)Removed on label approval, named in the release comment; added after the acceptance it is kept like a person’sParked → no sign-offn/a
needs-human added by a person (or unreadable timeline)Kept on a label-driven repo: the lifecycle bot owns it, and only a person removes it; the issue stays derived at 045 and out of the agent queue. (Elsewhere /hive approve / /hive decision / /fixed lift it whoever added it — docs#419.)Parked → no sign-offn/a
retired needs-decision / needs-direction (#12683)Migrated by the issue stage reconciler: stage/045-needs-decision added, retired label removed; a person’s retired label therefore becomes a Hive-added 045 and /hive approve can clear itParked → no sign-offn/a
hold, do-not-mergeKept; issue stays parked (unchanged)Hold (unchanged)n/a

How the hive sees comments

The un-park path is polling, not a webhook: every sweep lists open issues, keeps the “What to reply” notice on issues parked by needs-human or stage/045-needs-decision, and then considers the newest eligible comments within a bounded seven-day window and a per-sweep action cap. Agents may still read issue threads directly in their prompts, but the deterministic label transition to approved-direction happens only when the sweep accepts /hive approve or /hive decision <text>.

PR approval command feedback

Hive answers recent /hive approve comments on open PRs once per comment, including PRs without a parking label (#13087). Its reply acknowledges the comment and names the lever that actually releases a requires_human hold on this release line — a trusted merger’s GitHub Approve review on the current head — or explains why the lane cannot act on it: for example, the commenter is not a trusted merger (on any merge lane — contributor, trusted-author or hive-authored — since only a trusted merger’s Approve releases a hold), the contributor-lane verdict is a rejection rather than requires_human, or the PR touches a manual-only path. An ordinary contributor cannot release their own PR.

The acknowledgement does not merge the PR, remove labels, or bypass any merge gate; no merge lane consumes /hive approve on a PR. stage/085-needs-decision comments name the action for that lane under How to release it, including the GitHub Approve review when that is the lever, and explicitly identify manual-only merges such as workflow edits, removed tests or configured human-merge paths.