Skip to content

[scanner] meta: merge-eligible contributor PRs refused every kick by contributor-lane:no-claim (dibs#602/#603, hive#16687/#16691/#16680) #16717

Closed

Description

@hivecommons-hive

Summary

Every scanner kick since 2026-11-05T00:04Z has listed the same five contributor PRs as MERGE-ELIGIBLE (CI green, hive-reviewed approve), and every hive-merge request for them has been refused with the same policy error:

authorization denied: contributor-lane policy refuses the merge relay for @thatguywob's PR:
contributor-lane:no-claim (author tier "contributor", require_tiers merger, trusted)

Affected PRs (15+ consecutive refusals each, 2026-11-05 00:04Z → 04:12Z):

Why this is one incident, not five

The governor's merge-eligibility computation and the merge relay's contributor-lane policy disagree about the same class of PR: approved, CI-green PRs from a contributor-tier author whose relay record has no claim. The governor keeps dispatching them to the merge sweep; the relay keeps refusing; each kick burns five merge requests and a bead and nothing changes. Fixes already in flight (e.g. #16691 for the ntfy 429 selfreports #16689/#16708) sit unmerged behind it.

Asks (pick whichever is the intended behaviour)

  1. Eligibility side: exclude PRs the relay will refuse (contributor tier without a claim / not in require_tiers) from the MERGE-ELIGIBLE list, and surface them in a distinct "needs maintainer merge" section so lanes stop retrying.
  2. Relay side: if an approved, CI-green contributor PR that hive-review approved should be mergeable, treat the review approval (or a linked Closes #N on an issue the author held) as satisfying no-claim, or document the /claim step the author must take and have the relay say so in its refusal.
  3. Either way, the relay refusal should post one comment on the PR naming what unblocks it; today the refusal is visible only in the merge-request result file.

Decision taken by hive: filing as a tracker for the shared root cause rather than re-recording the refusal per kick; the lane will stop retrying these five until this closes or the policy/eligibility changes.

Evidence

  • /var/run/hive-metrics/merge-requests/scanner-1793851945662442632.result.json (dibs#602, 2026-11-05T04:12:28Z) and sibling results for the other four this kick, all ok:false with the identical error above.
  • Scanner beads 2026-11-05 00:04Z, 00:18Z, 01:21Z, 01:35Z, 01:47Z, 02:05Z, 02:21Z, 02:29Z, 02:59Z, 03:13Z, 03:28Z, 03:38Z, 03:48Z, 03:57Z, 04:06Z — same five PRs, same error.

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

Activity

  1. added
    agent/scannerCreated or modified by the scanner agent
    metaTracker for multiple open items sharing one root cause
    on Nov 5, 2026
  2. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 5, 2026
  3. hivecommons-hive commented on Nov 5, 2026

    @hivecommons-hive
    ContributorAuthor

    🔓 Claim by @thatguywob released (lease revoked).

    Claim history
    • 2026-11-05 04:24 UTC — claimed by thatguywob (contributor on hive hosted-available-oke-11-placeholder-r05x)
    • 2026-11-05 04:30 UTC — released by thatguywob (contributor; lease revoked)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent/scannerCreated or modified by the scanner agenthelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.metaTracker for multiple open items sharing one root cause

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions