Watch
0
0
Fork
You've already forked hyperhive
0

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:
atlas 2026-11-15 20:47:21 +01:00 • committed by mara
commit 1edeb5c55d

View file

@ -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.