Skip to content

✨ Hive re-authors its own fixer-exhausted PRs automatically; re-author pill becomes adopt #16582

Closed

Description

@clubanderson

What the operator saw

Row #16265 / PR #16456 (a hive-authored PR; the fixer gave up after 6 attempts) parked at 085 with inline pills Re-author ▸ and Let hive decide ▸.

we should not need a re-author pill on a hive agent's PR. And whenever we 're-author' it should be called 'adopt'.

Pressing the pill is also a dead end today: the decision API queues adoption/supersede, and the adoption sweep then refuses to supersede the App's own PR ("Not superseding: this PR is the hive's own"), so nothing happens.

What should happen

  1. Engine — hive re-authors its own exhausted PR automatically. When a hive-authored PR hits fixer-exhausted, the hive does not ask a person: it closes the PR as superseded (note + hive/superseded), labels the issue hive/re-authored, and lets the issue requeue so the next kick opens a fresh PR from the current base (the kick message says so and asks for Supersedes #<old>). Bounded to one automatic re-author per issue (store record + issue label); a second exhaustion parks at 085 with Give direction / Hand it to a person / Close as not planned only.
  2. Vocabulary. decide:re-author is removed from server options and UI labels. Where a person can have the hive rewrite a contributor's PR (DCO-unsigned head, exhausted contributor PR) that is decide:adopt — "Adopt as hive PR". Historical re-author ledger entries stay readable and map to adopt.
  3. Tracker words. While it runs the issue sits in the PR-in-progress lane as Re-authoring · superseding #N (remediation evidence kind kick, source re-author); the fresh hive PR carries lineage {kind: "re-authored", from_number} → chip "re-authored from #N". "adopted from #N" stays for contributor PRs the hive took over.

Evidence

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 4, 2026
  2. hivecommons-hive commented on Nov 4, 2026

    @hivecommons-hive
    Contributor

    🔓 Claim by @thatguywob released (lease revoked).

    Claim history
    • 2026-11-04 12:27 UTC — claimed by thatguywob (contributor on hive hosted-available-oke-11-placeholder-r05x)
    • 2026-11-04 12:28 UTC — released by thatguywob (contributor; lease revoked)
  3. added a commit that references this issue on Nov 4, 2026
    fcc4e98
  4. github-actions commented on Nov 4, 2026

    @github-actions
    Contributor

    @clubanderson this issue was closed by @hivecommons-hive[bot] as completed.

    If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.

    If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.

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

    enhancementNew feature or requesthelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions