Watch
0
0
Fork
You've already forked hyperhive
0

docs: the config repo grant is read in the persistence and forge handbook pages

This commit is contained in:
damocles 2026-11-16 01:08:03 +01:00 • committed by mara
commit 7b62f2c22a
2 changed files with 8 additions and 8 deletions

View file

@ -46,10 +46,11 @@ The tables, state directories, mounts and migrations behind this are in
A config change is a pull request on the agent's config repo, A config change is a pull request on the agent's config repo,
`agent-configs/<name>`. No tool exists for it: opening the PR is the request. `agent-configs/<name>`. No tool exists for it: opening the PR is the request.
1. The agent clones its config repo, edits it (`agent.nix` is the entry point), 1. The agent clones its config repo, edits it (`agent.nix` is the entry point)
pushes a branch and opens the PR with `hive-forge`. Branch protection lets it and opens the PR with `hive-forge pr create --agit`. It has read access to
push branches but not `main`, so it **can't merge its own config PR**. An agent the repo and no push access, so it **can't push a branch or merge its own
can propose a change to another agent's config the same way. config PR**. An agent can propose a change to another agent's config the same
way.
2. You review the PR on the forge, with its diff, comments and CI status, and 2. You review the PR on the forge, with its diff, comments and CI status, and
merge it there. Merging needs membership of the `operators` team in merge it there. Merging needs membership of the `operators` team in
`agent-configs`. The team starts empty: add each operator by hand in the forge `agent-configs`. The team starts empty: add each operator by hand in the forge

View file

@ -48,10 +48,9 @@ forge is re-minted within five minutes.
Two things live in the `agent-configs` Forgejo organization: Two things live in the `agent-configs` Forgejo organization:
- A config repo per agent, `agent-configs/<name>`. The agent can push - A config repo per agent, `agent-configs/<name>`. The agent is a read
config-change branches and open config PRs there, but `main` is collaborator there: it opens config PRs through the AGit flow, has no push
branch-protected: only the `operators` team can merge, and the agent can access, and only the `operators` team can merge, so it can't self-merge. An operator's merge in the Forgejo UI
neither push `main` nor self-merge. An operator's merge in the Forgejo UI
deploys the merged commit (see deploys the merged commit (see
[persistence.md § Config changes](../agents/persistence.md#config-changes)). [persistence.md § Config changes](../agents/persistence.md#config-changes)).
Repos stay private, so an agent can't read another agent's config. Repos stay private, so an agent can't read another agent's config.