docs: the config repo grant is read in the persistence and forge handbook pages
This commit is contained in:
parent
51283b8cb1
commit
7b62f2c22a
1 changed files with 8 additions and 8 deletions
|
|
@ -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,
|
||||
`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),
|
||||
pushes a branch and opens the PR with `hive-forge`. Branch protection lets it
|
||||
push branches but not `main`, so it **can't merge its own config PR**. An agent
|
||||
can propose a change to another agent's config the same way.
|
||||
1. The agent clones its config repo, edits it (`agent.nix` is the entry point)
|
||||
and opens the PR with `hive-forge pr create --agit`. It has read access to
|
||||
the repo and no push access, so it **can't push a branch or merge its own
|
||||
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
|
||||
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
|
||||
|
|
|
|||
Loading…
Reference in a new issue