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