Skip to content

✨ Remote repos: per-hive write identity (bot, bot only, or owner) #18516

Closed

Description

@clubanderson

Follow-up to #18196 (children #18197-#18200).

Since #18202, every write a hive makes on a remote (reference, write-tier) repo appears under the hive owner's own GitHub account. A hive owner raised a provenance concern: the owner commissioned the work, they did not do it, and the issues and PRs should say so.

Decision

A per-hive setting, project.remote_write_identity, with three values:

Value On a granted repo where the hive's App is installed Where the App is not installed
bot (default, also what a missing key means) posts as the App bot owner's connected account if connected, else read-only
bot_only posts as the App bot read-only, never the owner's token
owner owner's connected account owner's connected account (today's behaviour)
  • The App is never requested or pushed on anyone. The hive only detects an installation the repo's owner already made.
  • The setting never widens a grant. Only entries already at the write tier (hand-written, or derived from an accepted request issue per 📝 RFC: derive write-tier reference repos from an accepted assessment request issue (no hub, no token on the spoke) #18139) get a credential. An App installation shared by many hives, such as the one on the hivecommons org, is not a grant by itself.
  • Bot tokens are minted on the installation covering that one repo, scoped to that repo, with only the permissions the write tier needs.
  • Every reference-repo proxy restriction stays as it is: no labels, reviews, assignees, closing other people's items, merges, default-branch pushes, scanning or kicks.
  • Settings → Repos → Reference repos gets an owner-only control and a per-repo line showing which identity applies and why. Changes are audit-logged.

Plan

  1. Backend: config key, identity resolution, App mint, proxy credential per policy, kick text, tests.
  2. Settings API and UI, docs (two-lane section, api-reference, openapi).

Upgrade behaviour

Existing hives have no key, so they read as bot. A repo where the App is not installed behaves the same as today. A granted repo where the App is installed (for example the hivecommons repos derived from cncf/techdocs#395) switches from the owner's account to the App bot. That is the intended change.

Activity

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

    @hivecommons-hive
    Contributor

    🔓 Claim by @Karibhou released (covering PR merged or closed).

    Claim history
    • 2026-11-16 21:38 UTC — claimed by Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x)
    • 2026-11-17 02:30 UTC — released by Karibhou (contributor; covering PR merged or closed)
  3. hivecommons-hive commented on Nov 16, 2026

    @hivecommons-hive
    Contributor

    PR #18521 covers this issue: #18521

    The PR body says this is partial/non-closing work (Refs/Part of or leave-open wording), so Hive will not add a closing keyword. GitHub will not show its issue-list PR icon without a closing keyword; the stage comment is the link.

  4. clubanderson commented on Nov 16, 2026

    @clubanderson
    MemberAuthor

    @nate-double-u this is the setting from our chat: each hive chooses how it posts on other projects, "Hive bot, falling back to me" (default), "Hive bot only" (never posts as you; read-only where the App isn't installed), or "Me". Backend is #18521; the Settings choice follows. For your hive, "Hive bot only" gives you what you described.

  5. nate-double-u commented on Nov 16, 2026

    @nate-double-u
    Contributor

    Thanks @clubanderson, this looks like a good solution to our chat.

  6. github-actions commented on Nov 17, 2026

    @github-actions
    Contributor

    @clubanderson this issue was closed by @kubestellar-prow[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.

  7. added
    hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation
    and removed on Nov 17, 2026
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

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmationtriage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions