gt-secret-set1

Usage

Overview

Create or update a secret.

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.

Setting an existing secret without --description clears its description.

description, name

Options

--account[=false]
Use the secrets 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 secrets 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

Examples

# paste the value of a repository secret at a prompt
$ gt secret set DEPLOY_TOKEN
# set an organization secret from standard input
$ echo -n "$TOKEN" | gt secret set NPM_TOKEN --org acme
# set the secrets of a dotenv file
$ gt secret set --env-file .env