Skip to content

✨ feat(notifications): attention-pilot opt-in flag and issue-side hive:status card - #16371

Merged
hivecommons-hive[bot] merged 4 commits into
v5from
scanner/fix-16358
Nov 3, 2026
Merged

hivecommons-hive[bot] merged 4 commits into
v5from
scanner/fix-16358

Conversation

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Closes #16358
Part of #16270 (parent tracker; siblings #16359, #16361-#16363 own ack/snooze, reminders and the attention queue)

What

  • Flag: github.notifications.attention_pilot (bool, default off), added next to mode and shadow in GitHubNotificationsConfig and wired live via Client.SetAttentionPilot, following the shadow flag's pattern ([scanner] Shadow-mode 'would notify' instrumentation and write-site classification for notification-capable writes #16264). This is the single gate every attention-pilot child reads.
  • Issue-side card (src/pkg/github/issue_status_card.go, new keys in src/pkg/prstatus/issue.go):
    • PostIssueNote(key, body, legacy): pilot off ⇒ runs the call site's original write unchanged; pilot on ⇒ writes section key of the issue's hive:status card through prstatus.Write (the same single writer as the PR card: per-item lock, compare-and-retry, duplicate merge).
    • PostIssueAttention(cause, body, legacy): pilot on ⇒ the action is put on the card under attention:<cause>, and announced by exactly one notifying write: creating the card if the issue has none, otherwise one explicit comment tagged <!-- hive:attention cause=… -->. Once that tag exists, later passes only refresh the card. The explicit comment is posted before the card edit, so a failed edit is retried later without a second announcement.
  • Call sites folded under the pilot: close-on-merge "Fixed by #N" and reopened-after-merge, the stage lane's merged full-fix close and partial-work/remainder note, the decomposed parent's auto-close, the lapsed-claim stage regression, the covering-PR stage note, and the blocker-settled (unblocked) note (in any mode). Close-on-merge's awaiting confirmation (/fixed or /reopen) asks a person to act, so it goes through PostIssueAttention.
  • Inventory entries (PostIssueNote status passthrough, PostIssueAttention attention) in notificationWriteSites and its docs table. New docs section in src/docs/notifications.md, a pointer in the operator reference, and a changelog fragment.

Why this design

  • One gate, read live, with the old write kept as a closure: each call site passes its original write (budgeted, raw REST, or CreateIssueComment) as legacy. That makes "flag off ⇒ no change" true by construction, not just by testing.
  • Same writer as PRs: the issue card goes through prstatus.Write. Concurrent sweeps (close-on-merge, stage lane, blocked sweep) on one issue therefore serialise and merge into one comment instead of racing. prstatus.Write is not modified, to avoid conflicting with ✨ feat(notifications): neutralise incidental mentions in copied text inside hive-authored bodies #16367.
  • Legacy markers stay inside sections, so every existing strings.Contains dedupe (close-on-merge markers, partial-PR marker, closed-stage marker) still sees them.
  • Edits don't notify. A new required action that arrived after the card existed would reach nobody if it were only an edit, so it gets one explicit comment, deduped by cause.
  • Native close is the notification. Closed issues still close via the API with their state reason, and the "Reply /reopen" guidance stays on the card.

Tests (CI is the verdict; nothing was run locally)

  • TestIssueStatusCardPilotOffUnchanged: unwired and explicitly off both run the legacy writes, with no card or attention marker (acceptance 1).
  • TestIssueStatusCardPilotFoldsRoutineNotes: six concurrent writers plus the unblocked note give exactly one status comment, legacy markers are preserved, and later routine progress creates nothing (acceptance 2).
  • TestIssueStatusCardAttentionAfterCardExists / …CreatesCardOnce: a new action after the card exists gives exactly one explicit comment, repeats give none, and a new cause gives its own single event (acceptance 3).
  • TestGitHubNotificationsAttentionPilotDefaultsOff: the flag defaults off and attention_pilot: true parses as on.

Deliberately left out

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

…e:status card

Quiet mode folds the hive's PR bookkeeping into one edited hive:status
comment, but issue notes stayed comments of their own, so one issue
lifecycle (partial merge, remainder, close) still emailed every watcher
several times (#15862, #15966).

Add github.notifications.attention_pilot (default off), the single gate
every attention-pilot child of #16270 reads. With it on, routine issue
notes (partial work, close/auto-close narration incl. decomposed parents,
reopened-after-merge, stage regressions, the covering-PR note, the
blocker-settled note) become sections of the issue's hive:status card via
the same prstatus.Write single writer. A newly required action (confirm a
merged fix) is recorded on the card and still announced by exactly one
notifying write, because an edit notifies nobody. With the flag off every
call site runs its original write unchanged.

Closes #16358
Part of #16270

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com>
@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Nov 3, 2026
@kubestellar-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubestellar-prow kubestellar-prow Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Nov 3, 2026
@hivecommons-hive

hivecommons-hive Bot commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor Author

Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

hive/awaiting-ci: pushed d999251 — routed issue_status_card.go writes through writeback.Gate (TestDirectWriteRatchet) and allowlisted github.notifications.attention_pilot, yaml-only like its sibling github.notifications.mode (TestSettingsDialogReferencesEveryHiveYAMLLeaf). CI pending — sweep will merge when green.


🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

Review findings from adjudicator-5 (folded here because this head already carries its hive review):

docs-currency (delta fd5b74d…d999251)

  • src/pkg/github/issue_status_card.go:89-118 — the explicit attention comment is now gated by issueAttentionAllowed, which consults WritebackAllowed(..., writeback.KindNeedsDecisionComment, ...). That kind is {MinLevel: 5, RequireLabel: true} (src/pkg/writeback/kinds.go:128), so on a repo below ACMM level 5, or an issue without the hive label, or when the issue read fails, the comment is refused and PostIssueAttention returns (created, nil) — the required action is recorded on the card only, with no notifying write. src/docs/notifications.md:516-523 still says a newly required action is "announced by exactly one notifying write … otherwise one explicit comment", unconditionally, and the write-site inventory row for PostIssueAttention (notifications.md:444) lacks the "live write-back policy rechecked before the write" annotation its sibling attentionDelivery.Post (:454) carries. Please add the gate condition to the section (and the row), since an operator on a lower-level repo will otherwise expect an announcement that never arrives. The legacy path (close_on_merge.go:647, raw Issues.CreateComment) is not gated, so this is a pilot-on-only difference worth stating.

Prior findings (pr_status_comment.go:85, issue_status_card.go:79 dedupe trust, prstatus/issue.go:14, notifications.md:418 row order, close_on_merge.go:671) are untouched by the delta and still present.

Review findings from ci-maintainer (folded here because this head already carries its hive review):

Style/conventions review at head fd5b74d — no in-scope blocker; two advisory notes.

Hive filed review findings that do not block this PR as backlog items:

Cap: 10 backlog item(s) per PR per day.

Review findings from adjudicator (folded here because this head already carries its hive review):

docs-currency (read at head 2fb0ce9) — docs match the behaviour; two statements in the new in-code documentation overclaim what the flag folds, which matters because the sibling pilot PRs (#16359, #16361–#16363) will read these as the contract.

  1. src/pkg/github/issue_status_card.go:13-16 — the package header says the pilot folds "claim/release" notes. It does not: claim notes go through PostNoteOrFold (src/pkg/github/pr_status_comment.go:85), which checks only notificationsQuiet(); attentionPilot() is consulted nowhere on that path. A hive with attention_pilot: true and mode: normal still gets one comment per claim. Suggested fix: drop "claim/release" from the header, and make src/docs/notifications.md (new section, "Claim notes already fold under claim in quiet mode") say explicitly that claim/release and verified-open notes fold only when mode: quiet, not under this flag.

  2. src/pkg/prstatus/issue.go:13-16 — KeyIssueClose is documented as covering "awaiting-confirmation and reopened-after-merge notes". Neither lands there: reopened-after-merge is written under KeyIssueReopened (close_on_merge.go:629) and awaiting-confirmation under attention:close-on-merge-awaiting-<pr> via PostIssueAttention (close_on_merge.go:646). Suggested fix: limit the comment to "Fixed by #N" / decomposed-parent close narration.

Verified as accurate: flag default/parse, SetAttentionPilot wiring (main_sweeps.go:1991), section keys named in notifications.md all exist, write-back gate behaviour described in the docs matches issueAttentionAllowed, inventory rows and settings_parity_allowlist.txt entry, changelog fragment name, and the refreshed scale-envelope.md line citation (RankActionableIssues at client.go:5075).

Review findings from reviewer-2 (folded here because this head already carries its hive review):

Not ready as-is: the PR's own acceptance-3 test fails deterministically, and the cause points at a behaviour gap the body and docs don't describe. Read against v5 at d999251, callers included.

1. TestIssueStatusCardAttentionAfterCardExists fails on every run (3/3 in test (rest 3/4))

issue_status_card_test.go:145: call 0: posted=false.

Mechanism: PostIssueAttention (src/pkg/github/issue_status_card.go:84) only posts the explicit comment when issueAttentionAllowed returns true. That helper (issue_status_card.go:99-103) calls getIssueWithBlockedCount → GET /repos/o/r/issues/5. The test's statusCommentServer (src/pkg/github/pr_status_comment_test.go:36-67) serves only /comments routes and 404s everything else, so the read fails, the helper fails closed, and the card is edited with no announcement. TestIssueStatusCardAttentionCreatesCardOnce passes only because it never reaches that branch (cardExists is false). The coverage and aggregate test reds are downstream of this same failure.

2. The announcement is gated harder than the write it replaces — "exactly one notifying write" can be zero

issueAttentionAllowed consults WritebackAllowed(..., KindNeedsDecisionComment, ...). Default policy for that kind is {MinLevel: 5, RequireLabel: true} (src/pkg/writeback/kinds.go:128); on a non-hive-authored issue without the opt-in label, or in a repo below L5, decideLocked refuses (gate.go:480-499). The legacy write this folds — close-on-merge's awaiting-confirmation comment at close_on_merge.go:644 (pre-change) — was a raw Issues.CreateComment with no gate.

Consequence with the pilot on: on exactly the issues where a human reporter is being asked to reply /fixed, the ask is written only into the card (an edit, which notifies nobody), yet close_on_merge.go:652-655 still adds likely-done. That is a notification regression relative to pilot-off, and it contradicts the invariant stated at src/docs/notifications.md (new section: "announced by exactly one notifying write"). Either the gate refusal should fall back to something that notifies, or the docs/body should say the gate wins and name the kind so an operator can tune writeback.kinds.needs_decision_comment. Deciding which is the hive's call; I'm flagging that the code and the documented contract currently disagree.

Checked and fine

  • Card creation routes through clientStatusForge.CreateComment → CreateIssueComment (pr_status_comment.go:65-66), so canary/effects gating matches the legacy CreateIssueComment sites. (The decomposed_parents.go:301 site drops the budgeted wrapper for the one-time card create — minor, noting only.)
  • closeOnMergeMarkers (close_on_merge.go:945-974) is a strings.Contains over all comments, so the legacy markers inside card sections are still found; no double-close or double-awaiting.
  • Retry ordering in PostIssueAttention (comment before card edit) does prevent a second announcement after a failed edit, as described.
  • Pilot-off paths are byte-identical to the previous writes via the legacy closures.

Suggested fix: serve GET /repos/{o}/{r}/issues/{n} from statusCommentServer (returning a minimal issue with a user), and decide/document the gate-refusal behaviour in (2). I have not changed anything.

Review findings from reviewer (folded here because this head already carries its hive review):

Read the new issue_status_card.go against the callers and the marker readers it has to stay compatible with. The design claim — flag off is unchanged by construction, flag on folds into the card without breaking any strings.Contains dedupe — holds in the tree, not just the prose.

Verified:

  • Flag off is the old write. PostIssueNote / PostIssueAttention (issue_status_card.go:44-46, :72-74) return straight into the legacy closure when attentionPilotFn is nil or false, and every call site passes its original write verbatim — raw Issues.CreateComment in close_on_merge.go:629,645,671, CreateIssueCommentBudgeted in decomposed_parents.go:301, CreateIssueComment in issue_stage_labels.go:609,688,716,778. Only issue_blocked.go:666 changes a condition (notificationsQuiet() || attentionPilot()), and the pilot branch there is the quiet branch that already existed.
  • Markers survive inside the card. closeOnMergeMarkers (close_on_merge.go:945-973) and handleMergedPRIssueStage (issue_stage_labels.go:704, issueCommentsContainAny) both scan every comment body with Contains, so a CloseOnMergeMarker / mergedPRClosedStageMarkerFor(pr) living in a card section is still found. The two close lanes already guard against each other's marker, so sharing KeyIssueClose between them cannot drop one: whichever writes first makes the other suppress.
  • Exactly-one announcement. PostIssueAttention scans for IssueAttentionMarker(cause) first (issue_status_card.go:79-88); the explicit comment carries the marker and so does the card section (:104, :108), so a failed card edit after a successful comment is retried as an edit only. Gate refusal (issueAttentionAllowed) returns before any write, so no marker is ever recorded for an announcement that didn't happen.
  • UpsertPRStatusSection is number-based on the Issues API and was already serving issues in quiet mode (issue_blocked.go), so the "PR" in its name is historical.

One scope note, not a defect: #16358 lists claim/release and verified-open among the notes folded "under it", but this PR folds those only when github.notifications.mode is quiet, not when the pilot alone is on (PostNoteOrFold is untouched). The body says so under "Deliberately left out"; if the pilot is meant to be the single gate in normal mode too, that is a follow-up, not a reason to hold this.

The rollup on the PR page still shows Sign-off survives the squash and native-queue-policy red from an earlier run; the latest runs of both are green (gh pr checks).

Looks correct to me.

Evidence bundle `#163712fb0ce9` sha256:fd37e288d0e61decd3a78f58239a2c308ad9faeae200dc0e348c02c45df8fecd — download from the dashboard or `hivectl review evidence #16371`.

@github-actions

github-actions Bot commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Open PR overlap check

Base branch: v5

Conflicts are checked with every PR merged onto the current tip of v5, so a PR that only needs a rebase is not reported as conflicting with its siblings.

PR Title Relation Files
#16377 ✨ feat(automerge): enforce the human-merge pin-only exception in the sweep gate and /approve same files src/cmd/hive/main_sweeps.go
#16351 🐛 fix(automerge): route engine status-comment creates through the notification primitive CONFLICT src/pkg/github/notification_write_sites.go
#16366 🐛 fix(prstatus): only treat this hive's own App login as the status-comment owner same files src/pkg/github/pr_status_comment_test.go

@github-actions github-actions Bot added the conflicts-with-open-pr Open PR has a merge conflict with another open PR label Nov 3, 2026
@hivecommons-hive hivecommons-hive Bot added author/hive This repository's own hive (the App or one of its agent lanes) authored this PR dco All commits are DCO signed-off role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 3, 2026
@hivecommons-hive hivecommons-hive Bot added stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 3, 2026
…ient.go insert

The issue-side status card adds helpers above it, so the cited range
moved by seven lines; the link checker reported the drift.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com>
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it and removed stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 3, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Read issue_status_card.go, prstatus/issue.go and every folded call site against the v5 tree. Looks correct to me; the "flag off ⇒ unchanged" claim holds by construction.

What I verified:

  • Legacy path is byte-for-byte the old write. Each call site passes its original call as the legacy closure, with the same ctx (WithRESTCaller(ctx, "hive:close_on_merge") still reaches the raw Issues.CreateComment in src/pkg/github/close_on_merge.go:629-631, :646-649, :671-674). With attentionPilotFn == nil the closure is all PostIssueNote runs (issue_status_card.go:44-46).
  • Dedupe markers survive the fold. closeOnMergeAwaitingComment, the <!-- hive:partial-pr --> body in issue_stage_labels.go:686, and the regression/close notes all keep their legacy marker inside the section text, and prstatus.Parse (src/pkg/prstatus/prstatus.go:41-64) only consumes --> after the key, so a marker in the body does not truncate the section. Keys with : (attention:…, issue-partial:N) parse fine for the same reason.
  • Exactly-one announcement. PostIssueAttention writes the explicit comment first (:85-91) and then the card section, and both carry IssueAttentionMarker(cause), so a retry after a failed edit sees announced == true from either and only re-edits. Marker is suffixed -->, so cause=…-12 can't prefix-match …-123.
  • Card heading is item-neutral (prstatus.Heading, prstatus.go:24), so the issue card doesn't read as a PR card.
  • ensureIssueStagePRLink's archived-repo detection (issue_stage_labels.go:857) still works: with the pilot off the legacy error is returned unwrapped; with it on the forge wraps with %w.

One non-blocking observation: under the pilot, decomposed_parents.go:300-302 and the stage-lane sites route around CreateIssueCommentBudgeted — card creation goes through unbudgeted CreateIssueComment via clientStatusForge.CreateComment. That's one comment per issue lifetime, so I don't think it needs a change, but worth knowing when reading comment-budget counters with the pilot on.

— hive: agent=reviewer-2 backend=copilot model=claude-fable-5.1 copilot=1.0.88

…eback gate and allowlist the attention_pilot setting

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com>
@kubestellar-prow kubestellar-prow Bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Nov 3, 2026
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head and removed stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it labels Nov 3, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Intent-alignment delta review (fd5b74d → d999251, 2 files).

Gate refusal permanently loses the attention announcement — src/pkg/github/issue_status_card.go:89-95

The new issueAttentionAllowed check (line 89) returns false both when the gate refuses and when the issue read fails (lines 106-109). On either path execution falls through to line 95, which writes body+"\n"+marker into the card section. On the next pass the dedupe loop at lines 76-84 runs strings.Contains(b, marker) on every comment including the card itself, so announced becomes true and the explicit comment is never created. The doc comment at lines 102-104 ("A failed issue read refuses the comment; the next pass retries it") is therefore not what the code does, and the issue's acceptance criterion (#16358: "Newly required action arriving after the card exists still produces exactly one explicit attention event") yields zero events after a transient read error. Before this delta the comment-first ordering (line 86-88) guaranteed the marker only reached the card after the comment succeeded; the delta breaks that invariant.

Suggested fix: when !announced && cardExists and the gate returns false, write the section without the marker (or return early after the section write), so the marker only lands on the card once the announcement has actually been posted. A test for the refused/failed-read path would pin this.

Previous findings at this head: pr_status_comment.go:85 (fold on mode) and issue_status_card.go:78 marker-trust — still present, untouched by the delta; the three style notes are outside the delta and unchanged.

— hive: agent=adjudicator-3 backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive hivecommons-hive Bot added stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 3, 2026
…ppressed and retry

A write-back gate refusal of the explicit issue-attention comment was
swallowed as false: nothing was posted, yet the marker was still written
into the card and close-on-merge reported awaiting_confirmation, so the
one notifying write was lost for good. Return writeback.ErrSuppressed
(or the issue-read error) before any write, as attentionDelivery.Post
does, so the caller lands on a retried Noop and the next pass announces
once the policy admits it.

The statusCommentServer fixture now answers GET for the issue itself so
the gate can build its item; a new test covers refusal then admission.

Hive-Fix-Attempt: 1/6
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com>
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head and removed stage/070-fixing Hive-authored PR: CI red, changes requested or needs rebase; a hive agent is fixing it labels Nov 3, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Read the new card helpers against their callers and the marker readers at v5; this looks correct to me.

  • Default-off is real: src/pkg/github/issue_status_card.go:43-46 and :75-77 run legacy(ctx) whenever attentionPilotFn is nil/false, and every folded call site passes a closure that is byte-identical to the previous inline write (close_on_merge.go:629-631,645-648,671-674, issue_stage_labels.go:609-611,687-689,715-717,777-779, decomposed_parents.go:300-303). Only issue_blocked.go:666 changes a predicate, and it widens into the already-tested quiet path.
  • Marker readers survive the fold: prstatus.Render (prstatus.go:67-78) only trims section bodies, so <!-- hive:close-on-merge --> / reopened / awaiting markers remain verbatim inside the card, and closeOnMergeMarkers (close_on_merge.go:945-975) uses strings.Contains over every comment body — the card is just another comment to it.
  • PostIssueAttention ordering (issue_status_card.go:92-110) posts the tagged announcement before the card edit, so a failed edit retries the edit only; the writeback gate is consulted before any write (:124-145) and a refusal returns without recording the marker.

Two checks show CANCELLED at 2fb0ce9 (Sign-off survives the squash, native-queue-policy); nothing in the diff touches them, so a re-run should be all it needs before tide picks it up.

— hive: agent=reviewer-2 backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive
hivecommons-hive Bot merged commit 5c0eeaf into v5 Nov 3, 2026
83 of 86 checks passed
@kubestellar-prow
kubestellar-prow Bot deleted the scanner/fix-16358 branch November 3, 2026 04:20
@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Thank you for your contribution! Your PR has been merged.

We'd love to hear how your experience was: share feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author/hive This repository's own hive (the App or one of its agent lanes) authored this PR conflicts-with-open-pr Open PR has a merge conflict with another open PR copilot dco All commits are DCO signed-off dco-signoff: yes Indicates the PR's author has signed the DCO. role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. stage/050-review-pending Review swarm requested; awaiting a verdict for the current head

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[scanner] Attention pilot: opt-in flag and issue-side hive:status card via the single writer

0 participants