Skip to content

🐛 Sentinel: a dashboard Approve releases the head for good; skip Prow-rejected /lgtm + /approve - #15216

Merged
clubanderson merged 2 commits into
v5from
fix/sentinel-release-memory
Oct 29, 2026
Merged

clubanderson merged 2 commits into
v5from
fix/sentinel-release-memory

Conversation

@clubanderson

Copy link
Copy Markdown
Member

Fixes #15214

Live (hivecommons/dibs#510): the owner clicked Approve in the dashboard at 00:32Z; the hive posted /lgtm + /approve (hive:pr-approval head=30e94a97) and removed sentinel-alert as its own account. At 00:33:56Z the sentinel sweep re-posted the full alert for the same head and re-applied the label; the contributor lane then skipped with contributor-lane:sentinel-blocked every cycle and the stage fell back to 085. The owner's approval was undone in two minutes.

Root cause: the alert comment was for the earlier head 674bcbb2; head 30e94a97 had no marker, so trySentinelPR fell through to sentinelClearedAfterLatestPush, which (correctly, #13602) refuses an unlabeled event whose actor is a hive account. The dashboard release was persisted only as the label removal and the human-change-request record — nothing the sentinel reads.

Fix

  • sentinelReleasedByDashboardApproval: the sweep reads the hive's own hive:pr-approval head=<sha> command comment (hive-authored only — markerAuthorTrusted) as the release for exactly that head, then recordSentinelClearance rewrites the marker comment as the released alert (new sentinelReleasedNote) so the 🐛 sentinel: cleared sentinel-alert label is re-applied on the next sweep #11686 restart path keeps it quiet. A later push has no approval bound to it and re-arms.
  • Lane side: already covered by 🐛 Activity Monitor: an owner's Approve admits the untrusted-author PR head — no adoption, merge as-is; DCO warned before acting #15156 (operator admission for the head). Once the label stays off, sentinel-blocked clears; untrusted-author-role is the trusted-author lane's normal skip for this author.
  • Prow repos where the bot is not an approver: when Prow has already answered the hive's own commands with "restricted to collaborators" / "NOT APPROVED" (quoting the hive comment id), a later Approve records the decision without re-posting the commands; PullRequestApprovalEvent.CommandsSkipped / response commands_skipped: prow-rejects-bot-commands, logged once per approval, toast reads Approval recorded; /lgtm + /approve not posted.

Tests

  • TestSweepSentinelDashboardApprovalReleasesHead: no re-apply across two fresh-client passes for the approved head; marker rewritten; push to a new head re-alerts.
  • TestSweepSentinelDashboardApprovalNotHonoured: forged approval by the author, and the hive's approval of an earlier head, both still re-alert.
  • TestRecordOperatorPullRequestApprovalSkipsCommandsProwRejected: lgtm-restricted / NOT APPROVED replies to the hive's comment skip the commands; replies to someone else, a human quoting the phrase, or no prior commands do not; the approval is recorded either way.
  • TestTrySweepContributorLaneOperatorApprovalAdmitsReleasedSentinel: the lane merges the newcomer-tier head on the recorded owner approval once the sentinel label stays off, and still stands down while it is on.

Docs: operator-reference.md (sentinel clearance), dashboard-sections.md (Approve row action). Changelog: changelog.d/fixed-sentinel-release-memory.md.

@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Oct 29, 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 nicholasjackson 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

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@clubanderson is auto-promoted for contributor-lane merging on this PR: the last 5 merged PRs by this author in this hive's repositories have no revert or sentinel-alert evidence. CI, reviewer verdict, diff fences, soak, holds and branch protection still apply.

@kubestellar-prow kubestellar-prow Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Oct 29, 2026
@github-actions

github-actions Bot commented Oct 29, 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
#15186 🐛 Activity Monitor: one coherent post-decision state for Let hive decide rows; 060 reviewed in CI / Review same files src/docs/dashboard-sections.md
src/docs/operator-reference.md
src/pkg/dashboard/api_repo_item_decision.go
src/pkg/github/pr_decision_operator.go
#15251 🐛 tracker: show Merging in the merge gate for at least the toast lifetime before ✓ same files src/docs/dashboard-sections.md
#15104 🐛 Activity Monitor: Rebase, then merge as maintainer; fixer owns parked conflicting PRs; dismiss self-inflicted changes_requested same files src/docs/dashboard-sections.md
src/docs/operator-reference.md
src/pkg/dashboard/api_repo_item_decision.go
#15134 🐛 Delegated decision on a capability gap: model the blocker, stop the un-park/re-park loop, name the missing App permission same files src/docs/dashboard-sections.md
src/docs/operator-reference.md
#15122 🐛 Write-back containment: per-kind gate for every unsolicited GitHub write, with backfill guard same files src/docs/operator-reference.md
src/pkg/github/sentinel_sweep.go
#15226 ✨ feature: enqueue eligible PRs into GitHub native merge queues same files src/pkg/github/automerge/automerge_contributor_lane_test.go
#15256 🐛 clanker PRs with a human changes-requested review show Returned to contributor, not Sentinel alert same files src/docs/dashboard-sections.md
src/pkg/dashboard/api_repo_item_decision.go
src/pkg/github/automerge/automerge_contributor_lane_test.go
src/pkg/github/pr_decision_operator.go
src/pkg/github/pr_decision_operator_test.go

@github-actions github-actions Bot added the conflicts-with-open-pr Open PR has a merge conflict with another open PR label Oct 29, 2026
@hivecommons-hive hivecommons-hive Bot added author/human A person pushed this PR themselves 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 Oct 29, 2026
@hivecommons-hive hivecommons-hive Bot added stage/071-needs-author Human-authored PR: CI red, changes requested or conflicting; diagnosis posted, the author must act and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Oct 29, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@clubanderson this PR is held at stage/071-needs-author and the hive will not merge it yet.

Failing checks:

  • test (rest 3/4)

Next: the hive does not push to your branch. Push a new head (or reply here); CI and the review swarm re-run automatically and the PR returns to the normal path.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

test (rest 3/4) is PR-local: TestRecordOperatorPullRequestApprovalSkipsCommandsProwRejected (src/pkg/github/pr_decision_operator_test.go:229) builds its unparkWireComment fixtures (ownLGTM, ownApprove, prowReply, the "human quoting the phrase" literal) without CreatedAt, so the fake serves "created_at": "" and go-github fails with

listing comments for org/repo#12968: parsing time "\"\"" as "\"2006-01-02T15:04:05Z07:00\"": cannot parse "\"" as "2006"

(24 occurrences, 3/3 runs, every subtest including prow_answered_someone_else). Fix: set CreatedAt: unparkNow() on each fixture (the other tests in issue_unpark_command_test.go do this, e.g. line 318), or give unparkWireComment.CreatedAt an omitempty tag so an unset field is omitted rather than serialised as an empty string. coverage / test are downstream of this shard.


🐝 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

@github-actions github-actions Bot removed the conflicts-with-open-pr Open PR has a merge conflict with another open PR label Oct 29, 2026
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head and removed stage/071-needs-author Human-authored PR: CI red, changes requested or conflicting; diagnosis posted, the author must act stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Oct 29, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Reviewed (security) — no blocking findings; one advisory.

  • sentinelReleasedByDashboardApproval (src/pkg/github/sentinel_clearance.go:113-131) gates a sentinel release on markerAuthorTrusted, which returns true for any author when knowsOwnAccounts() is false (src/pkg/github/label_approval.go:436-441 — a PAT hive with no identity and no /user). In that mode a PR author can post /lgtm + the exact attribution line + <!-- hive:pr-approval head=<sha> by=<owner> --> (format: pr_decision_operator.go:185-191) and release the alert on their own sensitive-path head. This is the same documented fallback the existing sentinel marker path already accepts (sentinel_sweep.go:569-575), so it is not a regression introduced here — but the doc comment at sentinel_clearance.go:111-112 ("Only comments the hive itself wrote count") overstates it. Consider failing closed for this authorization use since it is not a once-only idempotency marker:
		if comment == nil || !c.knowsOwnAccounts() || !c.isHiveAccount(comment.GetUser()) {

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

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@clubanderson this PR is held at stage/071-needs-author and the hive will not merge it yet.

Failing checks:

  • overlayfs-exec-guard

Next: the hive does not push to your branch. Push a new head (or reply here); CI and the review swarm re-run automatically and the PR returns to the normal path.

… skip Prow-rejected commands

A dashboard Approve takes the sentinel label off as the hive's own
account, so sentinelClearedAfterLatestPush (rightly) did not read the
unlabeled event as a human clearance and the sweep re-alerted the head
the owner had just approved (dibs#510, 00:32Z approved → 00:33Z
re-labelled). The sweep now reads the hive's own hive:pr-approval
head=<sha> command comment as the release for exactly that head and
rewrites its marker comment as the released alert, as the #13602 path
does; a new push re-arms. On a Prow repo where the bot is not an
approver, a later Approve records the decision without re-posting
/lgtm + /approve and reports commands_skipped.

Fixes #15214

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
Signed-off-by: Andrew Anderson <andy@clubanderson.com>
@clubanderson
clubanderson force-pushed the fix/sentinel-release-memory branch from 774986c to 06d8e79 Compare October 29, 2026 02:39
@hivecommons-hive hivecommons-hive Bot added stage/050-review-pending Review swarm requested; awaiting a verdict for the current head and removed stage/071-needs-author Human-authored PR: CI red, changes requested or conflicting; diagnosis posted, the author must act labels Oct 29, 2026
clubanderson added a commit that referenced this pull request Oct 29, 2026
…to contributor, not Sentinel alert

A trusted human's CHANGES_REQUESTED review on the current head of a
clanker-authored PR is the human the sentinel/hold/workflow-path parks
were waiting for: RouteHuman and ClassifyStage now route it to
stage/072-returned-to-contributor (071 for a person's PR, 070 for the
hive's) ahead of 085, and the contributor lane reads reviews before it
settles on sentinel-blocked. A new head re-arms the park (per head, as
in #15216).

Dashboard direction decisions are accepted on clanker PRs: the text is
recorded as a change request against the head, posted to the
contributor's hive, and the PR moves to 072; the 409 stays for a
person's PR only.

SPA: the 071/072 chevron keeps its routing word with the sentinel
finding as a suffix; Give direction names the contributor's hive.

Fixes #15255

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
@github-actions github-actions Bot added the conflicts-with-open-pr Open PR has a merge conflict with another open PR label Oct 29, 2026

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Security re-review at 06d8e795 (delta since 774986c3 is a rebase plus a test timestamp; the PR's own code is unchanged). No in-scope blocker; two prior advisories still stand:

  • src/pkg/github/sentinel_clearance.go:123 — sentinelReleasedByDashboardApproval gates on markerAuthorTrusted, which (label_approval.go:436-441) falls back to any author when knowsOwnAccounts() is false. In that degraded config a PR author can post /approve + Posted by @… + <!-- hive:pr-approval head=<own head> … --> and release their own sentinel alert. Same exposure already exists for the SentinelMarker path at :197, so not a regression; the forged-author test (sentinel_sweep_test.go, TestSweepSentinelDashboardApprovalNotHonoured) only covers the identity-known case. Fail closed for this new gate:
    		if comment == nil || !c.knowsOwnAccounts() || !c.isHiveAccount(comment.GetUser()) {
    
  • src/pkg/github/pr_decision_operator.go:104-134 — prowRejectedHiveCommands now requires a non-hive Bot-typed/[bot] author quoting a hive command id, so humans can't trigger it (test human quoting the phrase). Any other installed bot still can; effect is only that /lgtm+/approve are not posted while the approval is still recorded and the toast says so — fail-safe, low.

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

@hivecommons-hive

Copy link
Copy Markdown
Contributor

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

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

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Delta re-review (correctness) — read at head 06d8e79. The PR's own files (pr_decision_operator.go, sentinel_clearance.go, sentinel_sweep.go, api_repo_item_decision.go, the two test files) are byte-identical to the previously reviewed head 774986c; the delta is a rebase onto v5 plus created_at stamps on test fixtures. Both previous correctness findings are still present.

1. Prow-skip path leaves no head-bound approval comment, so the release never fires on the second approval (still present).
src/pkg/github/pr_decision_operator.go:324-329: when prowRejectedHiveCommands is true, nothing is posted. sentinelReleasedByDashboardApproval (src/pkg/github/sentinel_clearance.go:127) only releases on a hive-authored comment whose marker head= equals the current head, and trySentinelPR falls back to it at src/pkg/github/sentinel_sweep.go:451-456. prowRejectedHiveCommands can only be true when the hive already posted commands for an earlier head — so the exact dibs#510 sequence (alert → push → Approve) on its second occurrence on the same PR records commands_skipped and the sweep re-alerts the approved head within one pass. The same gap hits the workflow-path fence: src/pkg/github/automerge/automerge_contributor_workflow_approval.go:146-147 requires a hive /approve comment bound to the head, and dibs#510 touched .github/workflows/ci.yml.

Concrete fix — post one hive-authored, head-bound record comment instead of the commands, and let the parser accept it:

--- a/src/pkg/github/pr_decision_operator.go
+++ b/src/pkg/github/pr_decision_operator.go
@@ const PRApprovalCommandsSkippedProw = "prow-rejects-bot-commands"
+// prApprovalRecordHeading is the first line of the comment posted instead of
+// `/lgtm` + `/approve` when Prow rejects the bot's commands; it keeps the
+// head-bound marker the sentinel and the workflow fence read.
+const prApprovalRecordHeading = "Approval recorded"
@@ func ParsePRApprovalCommandComment(body string) (command, actor, head string, ok bool) {
 	known := false
 	for _, want := range PRApprovalCommands {
 		if command == want {
 			known = true
 		}
 	}
+	if command == prApprovalRecordHeading {
+		known = true
+	}
@@ func (c *Client) RecordOperatorPullRequestApprovalWith(
 	if prowRejected {
 		event.CommandsSkipped = PRApprovalCommandsSkippedProw
+		if err := c.CreateIssueComment(ctx, full, number, renderPRApprovalCommandComment(prApprovalRecordHeading, actor, head)); err != nil {
+			return PullRequestApprovalEvent{}, fmt.Errorf("recording approval on %s/%s#%d: %w", owner, name, number, err)
+		}

and in automerge_contributor_workflow_approval.go:147 accept command == prApprovalRecordHeading alongside /approve. prowRejectedHiveCommands and sentinelReleasedByDashboardApproval both go through the parser, so they pick the record comment up unchanged.

2. No test covers Approve-with-CommandsSkipped followed by a sweep (still present).
src/pkg/github/sentinel_sweep_test.go:560-700 has TestSweepSentinelDashboardApprovalReleasesHead / ...NotHonoured only; nothing in the file references CommandsSkipped or a Prow reply. A case that seeds a Prow rejection of an earlier-head command, approves the new head, and asserts no re-alert would have caught #1 and should land with the fix.

Security findings from the previous pass (sentinel_clearance.go:123 any-author marker when hive identity unknown; pr_decision_operator.go:112 third-party bot can suppress command posting) are also unchanged by the delta.

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

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The two halves of this PR undo each other on the repo it was written for. The sentinel release memory is keyed on a comment that the Prow-skip half stops writing.

  • src/pkg/github/sentinel_clearance.go:112-132 — sentinelReleasedByDashboardApproval finds the release only by locating a hive-authored comment whose ParsePRApprovalCommandComment head equals the current head, i.e. the <!-- hive:pr-approval … --> marker that renderPRApprovalCommandComment writes (pr_decision_operator.go:185). The sweep consults nothing else: SentinelAck does not appear in sentinel_sweep.go or sentinel_clearance.go, so RecordReviewEvidenceSentinelAck (pr_decision_operator.go:375) is not a fallback.
  • src/pkg/github/pr_decision_operator.go:320-330 — when prowRejectedHiveCommands is true, RecordOperatorPullRequestApprovalWith sets CommandsSkipped and posts no command comment, so no marker bound to the new head ever exists.

Mechanism, on dibs: the first Approve posted /lgtm + /approve and Prow replied "NOT APPROVED" quoting them (the dibs#510 state). Every later Approve on that PR — or on any later head — now hits the skip branch (prowRejectedHiveCommands only looks for a rejection of a hive command on the PR, not one for this head), writes nothing, and the sentinel sweep at sentinel_sweep.go:450-456 gets releasedBy == "", falls through, and re-posts the alert and re-applies the label as it did at 00:33Z. The incident this PR fixes recurs from the second approval onward on exactly the Prow repo where it was observed. Severity: high — the owner's approval is silently undone again. sentinel_sweep_test.go only covers the case where the command comment exists; pr_decision_operator_test.go:100-114 only asserts CommandsSkipped and Recorded, never the sentinel interaction.

Two ways out, either is small: (a) when skipping the commands, still post one hive-authored note carrying the hive:pr-approval marker for the head (no /lgtm//approve text, so Prow has nothing to reject) — the sweep then finds it; or (b) have sentinelReleasedByDashboardApproval also accept the review-evidence sentinel ack for head. A test with CommandsSkipped set followed by a sweep on the same head would fail today and pin the fix.

Minor, not blocking: prowRejectedHiveCommands is PR-wide, not head-bound, so a rejection on an old head suppresses the commands forever on that PR even if OWNERS later changes; probably acceptable but worth a comment.

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

@hivecommons-hive hivecommons-hive Bot added stage/071-needs-author Human-authored PR: CI red, changes requested or conflicting; diagnosis posted, the author must act and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Oct 29, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@clubanderson this PR is held at stage/071-needs-author and the hive will not merge it yet.

Why:

  • the review swarm requested changes

Next: the hive does not push to your branch. Push a new head (or reply here); CI and the review swarm re-run automatically and the PR returns to the normal path.

@github-actions github-actions Bot removed the conflicts-with-open-pr Open PR has a merge conflict with another open PR label Oct 29, 2026
@clubanderson
clubanderson merged commit 2f668ee into v5 Oct 29, 2026
79 of 83 checks passed
@kubestellar-prow
kubestellar-prow Bot deleted the fix/sentinel-release-memory branch October 29, 2026 03:08
@github-actions

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

clubanderson added a commit that referenced this pull request Oct 29, 2026
…to contributor, not Sentinel alert

A trusted human's CHANGES_REQUESTED review on the current head of a
clanker-authored PR is the human the sentinel/hold/workflow-path parks
were waiting for: RouteHuman and ClassifyStage now route it to
stage/072-returned-to-contributor (071 for a person's PR, 070 for the
hive's) ahead of 085, and the contributor lane reads reviews before it
settles on sentinel-blocked. A new head re-arms the park (per head, as
in #15216).

Dashboard direction decisions are accepted on clanker PRs: the text is
recorded as a change request against the head, posted to the
contributor's hive, and the PR moves to 072; the 409 stays for a
person's PR only.

SPA: the 071/072 chevron keeps its routing word with the sentinel
finding as a suffix; Give direction names the contributor's hive.

Fixes #15255

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
clubanderson added a commit that referenced this pull request Oct 29, 2026
…to contributor, not Sentinel alert

A trusted human's CHANGES_REQUESTED review on the current head of a
clanker-authored PR is the human the sentinel/hold/workflow-path parks
were waiting for: RouteHuman and ClassifyStage now route it to
stage/072-returned-to-contributor (071 for a person's PR, 070 for the
hive's) ahead of 085, and the contributor lane reads reviews before it
settles on sentinel-blocked. A new head re-arms the park (per head, as
in #15216).

Dashboard direction decisions are accepted on clanker PRs: the text is
recorded as a change request against the head, posted to the
contributor's hive, and the PR moves to 072; the 409 stays for a
person's PR only.

SPA: the 071/072 chevron keeps its routing word with the sentinel
finding as a suffix; Give direction names the contributor's hive.

Fixes #15255

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
clubanderson added a commit that referenced this pull request Oct 29, 2026
…contributor, not Sentinel alert (#15256)

* fix: clanker PRs with a human changes-requested review show Returned to contributor, not Sentinel alert

A trusted human's CHANGES_REQUESTED review on the current head of a
clanker-authored PR is the human the sentinel/hold/workflow-path parks
were waiting for: RouteHuman and ClassifyStage now route it to
stage/072-returned-to-contributor (071 for a person's PR, 070 for the
hive's) ahead of 085, and the contributor lane reads reviews before it
settles on sentinel-blocked. A new head re-arms the park (per head, as
in #15216).

Dashboard direction decisions are accepted on clanker PRs: the text is
recorded as a change request against the head, posted to the
contributor's hive, and the PR moves to 072; the 409 stays for a
person's PR only.

SPA: the 071/072 chevron keeps its routing word with the sentinel
finding as a suffix; Give direction names the contributor's hive.

Fixes #15255

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

* fix: honour a hand-placed stage/071/072 over the sentinel park for the current head

The reconciler logged added=[stage/085] removed=[stage/072-returned-to-
contributor] on hive#15159 after the owner swapped the labels by hand.
A trusted maintainer's return label the hive did not write is now read
from the label event once per head, recorded as a stage-label change
request against the head, and folded into the pass like a review, so
classification keeps 071/072 ahead of the sentinel/hold/workflow-path
parks; a new head re-arms the park. A standing change request in the
store now also folds into the stage detail when no reviewer verdict
was read for the head.

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

* fix: drop unused openPullRequestHead wrapper

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author/human A person pushed this PR themselves 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/L Denotes a PR that changes 100-499 lines, ignoring generated files. stage/071-needs-author Human-authored PR: CI red, changes requested or conflicting; diagnosis posted, the author must act

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🐛 Sentinel re-applies the alert to a head the owner just approved from the dashboard (dibs#510)

1 participant