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
2 changed files with 35 additions and 41 deletions
|
|
@ -125,7 +125,7 @@ checkpoints**, not about sandboxing the agent from its own tools:
|
|||
which swarm-controller converges on every config repo. An operator's merge
|
||||
there is also what deploys the config. Existing `agents/<repo>` repos carry
|
||||
the same merge gate.
|
||||
An agent (a write collaborator, not a repo admin) can neither change those
|
||||
An agent (a read collaborator, not a repo admin) can neither change those
|
||||
settings nor merge its own PR. It's **not** set up for external VCS (GitHub
|
||||
etc.), though — there, operator-merge is process + accepted risk, not a
|
||||
technical control.
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ agent gets every new item, and two of them would both label and assign it.
|
|||
creating a `triage` agent gives each new issue two todos. Switch one off on the
|
||||
board: the custom flow, or the archetype's flow
|
||||
([below](#on-the-board)).
|
||||
- **Forge rights.** A new agent's forge account is a write collaborator on its own
|
||||
- **Forge rights.** A new agent's forge account is a read collaborator on its own
|
||||
config repo and has read on `internal/docs`, and nothing else. Labelling and
|
||||
assigning an issue or a pull request in a project repo takes write access to
|
||||
that repo, so the triage agent can't do either until the operator adds it as a
|
||||
|
|
|
|||
Loading…
Reference in a new issue