raucao
8b5c216563
Cover the 1.0.0 command surface and stability guarantees: - New reference files: projects.md, runners.md, extensions.md - New commands: browse, project, runner, extension, upgrade, pr backport, pr update-branch, pr list --local, pr merge --method manually-merged, issue move, issue/pr comment attachment, webhook test - Global --csv output; exit codes 5 (run watch failed) and 6 (--expect-head) - Interactive edit forms for pr/label/release edit - Fix fork flag (--add-remote), clone flag (--upstream-remote-name), and org member subcommands (add -> conceal/publicize) - tea is archived; gt is the official successor; migration guide linked - Semver: 1.x keeps commands/flags/JSON fields/exit codes stable - Bump metadata/README to gt 1.0.0
3.0 KiB
3.0 KiB
Organizations and teams
Organization management and team access. gt <cmd> --help is authoritative.
Global flags are in SKILL.md.
org
gt org <command>
create delete edit list member view
org list aliases org ls; org delete aliases org rm.
JSON fields: description, full_name, id, location, name, repo_admin_change_team_access, visibility, website.
list [--all] [--username user] [-L n] [--page n]— your memberships by default, another user's with--username, every visible organization with--all.view <org>create <name> [-d description] [--full-name NAME] [--location LOC] [--website URL] [--visibility {public|limited|private}] [--repo-admins-can-change-team-access[=false]]edit <org>— ascreate, only the flags you pass change.delete <org> [-y]member {list|remove|conceal|publicize}— Gitea adds members through teams (gt team member add ORG/TEAM USER); a membership can be public or concealed.member list <org> [--public]checks each membership's visibility for administrators (one request per member) unless the output omits it.
gt org list
gt org list --all
gt org create acme --full-name "ACME Corp"
gt org create acme-internal --visibility private
gt org member list acme --public
gt org member conceal acme bob
team
gt team <command>
create delete edit list member repo view
Teams grant members access to an organization's repositories. team list
aliases team ls; team delete aliases team rm. In JSON, access is the
effective access shown in text (e.g. write, "write (code, issues, pulls)");
permission is the team-wide level Gitea reports (none for a team that grants
access per unit).
JSON fields: access, all_repositories, can_create_repo, description, id, name, organization, permission, units.
create <org> [<name>] [--name NAME] [--permission {read|write|admin}] [--unit repo.code=write,repo.wiki=read] [--all-repositories] [--can-create-repo] [-d description]—--permissiongrants every repository unit;--unitsets single units and overrides--permissionper unit.edit <team> [...]—--unitmerges into the current policy unless--unit-replaceis given.delete <team> [--force]—--forceallows deleting the owner team.view <team>,list <org> [-L n] [--page n]member {add|list|remove} <team> [<username>...]— a team isORG/TEAMor a numeric ID; adding a user also makes them an org member.repo {add|list|remove} <team> [<repository>...]— repositories named alone (service) orORG/NAME; removing from an all-repositories team has no effect until you turn that off withteam edit --all-repositories=false.
gt team create acme developers --permission write
gt team create acme/reviewers --unit repo.code=read,repo.pulls=write
gt team edit acme/developers --unit repo.wiki=write
gt team member add acme/developers bob
gt team repo add acme/developers service