gt-team-edit1

Usage

Overview

Edit a team. --permission sets every repository unit to read or write, or grants admin access. --unit changes single units and keeps the others, unless --unit-replace is passed. Only the description of an organization's owner team can be edited.

A team can be supplied as ORG/TEAM, such as acme/developers, where TEAM is the team's
name or ID, or as its numeric ID alone.

access, all_repositories, can_create_repo, description, id, name,
organization, permission, units

Options

--all-repositories[=false]
Access every organization repository (use =false to revoke)

--can-create-repo[=false]
Allow creating organization repositories (use =false to revoke)

-d, --description=""
Team description

-h, --help[=false]
help for edit

--name=""
Team name

--permission=""
Access to every repository unit; admin also manages repositories {read|write|admin}

--unit=[]
Unit access to change, such as repo.wiki=write; merged into the current policy

--unit-replace[=false]
Replace the whole unit policy with --unit; omitted units lose access

Options inherited from parent commands

--csv[=""]
Output CSV with the specified comma-separated fields, or all fields

--debug[=false]
Log the method, URL, status, and duration of each HTTP request to stderr

--host=""
Gitea instance URL, including any base path

--interactive[=false]
Allow prompts with machine output

-q, --jq=""
Filter JSON output using a jq expression; implies --json

--json[=""]
Output JSON with the specified comma-separated fields, or all fields

--no-input[=false]
Disable prompts and implicit editor/browser interactions

--sudo=""
Perform API requests as this user (requires an administrator account)

--user=""
Account name on the selected instance

Examples

$ gt team edit acme/developers --permission write
# also let the team edit the wiki
$ gt team edit acme/developers --unit repo.wiki=write
$ gt team edit acme/developers --name devs --description "Core developers"