| GT-VARIABLE-SET(1) | gitea-cli Manual | GT-VARIABLE-SET(1) |
NAME
gt-variable-set - Create or update a variable
SYNOPSIS
gt variable set [<name>] [flags]
DESCRIPTION
Create or update a variable.
The value comes from --body, --body-file or standard input when it is not a terminal (one trailing line break is removed), or else from a prompt. --env-file sets every NAME=value of a dotenv file instead.
JSON FIELDS
description, name, value
OPTIONS
--account[=false] Use the variables of your user account instead of a repository or organization
-b, --body="" The value
-F, --body-file="" Read the value from a file, or - for standard input
-d, --description="" Description
-f, --env-file="" Set every NAME=value of a dotenv file, or - for standard input
-h, --help[=false] help for set
-o, --org="" Use the variables of an organization instead of a repository
OPTIONS INHERITED FROM PARENT COMMANDS
--csv[=""] Output CSV with the specified comma-separated fields, or all fields
--cwd="" Working directory for repository discovery
--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
--remote="" Git remote used for repository discovery
-R, --repo="" Select a repository as OWNER/REPO or URL
--sudo="" Perform API requests as this user (requires an administrator account)
--user="" Account name on the selected instance
EXAMPLE
# set a repository variable $ gt variable set ENVIRONMENT --body staging # set an organization variable from a file $ gt variable set CONFIG --org acme < config.json # set the variables of a dotenv file $ gt variable set --env-file .env
SEE ALSO
| Nov 2026 | gitea-cli |