agents get read, not write, on their own agent-configs repo; an existing grant is left alone
This commit is contained in:
parent
144d958208
commit
07c66e3a1c
1 changed files with 35 additions and 41 deletions
|
|
@ -63,8 +63,9 @@ live; tokens of other names are never touched.
|
|||
Two things live in the `agent-configs` Forgejo organization:
|
||||
|
||||
- A config repo per agent (`agent-configs/<name>`). The
|
||||
agent is a **write collaborator on its own** repo — it can push
|
||||
config-change branches and open config PRs — but `main` is
|
||||
agent is a **read collaborator on its own** repo: it clones it and
|
||||
opens config PRs through the AGit flow (`hive-forge pr create --agit`),
|
||||
which needs no push access. `main` is
|
||||
branch-protected by swarm-controller: the merge and approval
|
||||
allowlists are the `operators` team, and the agent can neither push
|
||||
`main` directly nor self-merge. An operator's merge in the Forgejo UI
|
||||
|
|
|
|||
Loading…
Reference in a new issue