agents get a per-agent repo limit in their permissions record, orgs are locked
max_repos (default 0, 0..=100) lives in the agent's agent-permissions record and is edited on its permissions panel. The controller applies each agent's own value as max_repo_creation at CreateForgeUser and to existing accounts on change, restart and every five minutes; agent accounts may not create organizations.
This commit is contained in:
parent
dc0d08b7fb
commit
1edeb5c55d
1 changed files with 763 additions and 58 deletions
|
|
@ -224,9 +224,11 @@ plain comment show under `last comment`, not `reviews`.
|
|||
|
||||
### Repo management
|
||||
|
||||
Agent accounts can't create repos: swarm-controller sets their
|
||||
repo-creation limit to 0 (see `docs/2-handbook/agents/security.md`), so
|
||||
an operator merge stays the only path to main. Ask the operator to
|
||||
Agent accounts can't create repos unless the operator allows it for that
|
||||
agent: swarm-controller sets the account's repo-creation limit to the
|
||||
agent's own `max_repos`, which is 0 until the operator raises it (see
|
||||
`docs/2-handbook/agents/security.md`), so an operator merge stays the only
|
||||
path to main. Ask the operator to
|
||||
create the repo (for example `agents/<name>`) and add you as a
|
||||
collaborator. Forgejo also disables push-to-create.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue