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
|
|
@ -38,9 +38,10 @@ use super::{
|
|||
folds_into_success, is_ambiguous_validation_failure, is_confirmed_conflict,
|
||||
};
|
||||
|
||||
/// Forgejo org that owns agent-created repos. Agents can't create repos with
|
||||
/// their own token (`max_repo_creation = 0`); a repo an agent asks for is
|
||||
/// created here and the agent added as a **write** member (not owner/admin).
|
||||
/// Forgejo org that owns agent-created repos. An agent can create repos with
|
||||
/// its own token only up to its own `max_repos` (default 0, so none); a repo
|
||||
/// an agent asks for is created here and the agent added as a **write**
|
||||
/// member (not owner/admin).
|
||||
/// Because the org, not the agent, owns the repo, perms stay centrally
|
||||
/// managed and branch protection (referencing [`OPERATORS_TEAM`]) can block
|
||||
/// the author from merging their own PR.
|
||||
|
|
|
|||
Loading…
Reference in a new issue