gt-team-create1

Usage

Overview

Create a team in an organization. Name it as the second argument, as ORG/NAME, or with --name.

--permission grants read or write access to every repository unit, or admin access. Use --unit to set single units instead, or to override some of them.

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 create

--name=""
Team name

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

--unit=[]
Unit access, such as repo.code=write,repo.wiki=read; overrides --permission per unit

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 create acme developers --permission write
$ gt team create acme/reviewers --unit repo.code=read,repo.pulls=write
# give the team access to every repository of the organization
$ gt team create acme ops --permission admin --all-repositories