bircni
ab3e91acd1
webhook create --events pushh created a webhook that fired on nothing, since Gitea drops unknown events, and unknown types or a Slack webhook without a channel failed with raw HTTP 422 errors. --events and --type now accept only what Gitea knows, list it in help and complete it, and a Slack webhook needs --config channel=. Events came back in a different order on every call; they are sorted now. Webhooks can be told apart again: list, view and JSON show the delivery URL without user information and query, and without the path for chat services whose paths carry tokens; view --reveal-url shows it whole. Tables collapse complete event groups such as pull_request (8). On a terminal, webhook edit no longer needs an authorization flag: since Gitea drops the stored header on every edit and never returns it, it asks for the header again and keeps it, and an empty answer suits webhooks without one. Without a terminal the edit still requires the flags. Edit flags lose the create defaults, the unsupported secret flags are hidden on edit, deletions name the webhook and its scope, and mutations print ✓ lines. terminal.View gains Bodyless for resources without a body. Signed-off-by: bircni <bircni@icloud.com>
T E A
The official CLI for Gitea
Tea manages repositories, issues, pull requests, releases, and other Gitea resources with explicit commands suitable for local development and CI.
tea auth login --host https://gitea.example.org --with-token < token-file
tea issue list --repo owner/repository
tea pr view 123 --repo owner/repository --json
tea alias set bugs 'issue list --label bug'
tea help
tea 1.0 is a breaking release: it requires Gitea 28 or newer, commands, flags and
output formats changed, it uses separate config.yml and hosts.yml files, and it
requires fresh authentication.
Existing combined configuration files are left untouched; archive the old file or
choose an isolated TEA_CONFIG_DIR before setup. See
Migrating to tea 1.0 for the old-to-new mapping.
Run tea --help or tea <command> --help for supported commands and flags; the
full reference, man pages, and shell completions ship in each release's docs archive.
Credentials use the operating-system keyring by default; explicitly
select --credential-store file when private file storage is needed. For CI,
supply GITEA_TOKEN and its instance through TEA_HOST or GITEA_INSTANCE_URL;
environment credentials are never persisted.
Installation
There are different ways to get tea:
-
Install via your system package manager:
-
Use the prebuilt binaries from dl.gitea.com
-
Install from source: see Compilation
-
Docker: Tea at docker hub
Log in to Gitea from tea
Gitea can use many different authentication schemes, and not every authentication method will work with every Gitea deployment. When you are a Gitea instance administrator you can tweak your settings to fit your use case. For the method that is most likely to work with any Gitea deployment use the following steps:
-
Open your Gitea instance in a web browser
-
Log in to Gitea in your web browser. Any MFA, IDP, or whatever else should be available this way.
-
In your "user settings", generate an application token with at least user read permissions. If you want to do anything useful with the token add additional permissions/scopes.
-
Save the token in a private file and run
tea auth login --host https://your-instance --with-token < token-file. Credentials use the operating-system keyring by default.
You should now be logged in to your gitea instance from tea.
Alternatively, tea auth login --host https://your-instance --oauth authorizes tea in your browser. OAuth may not be available on all Gitea deployments, and needs a browser on the machine running tea.
Shell completion
If you installed from source or the package does not provide the completions with it you can add them yourself with tea completion <shell> command. Completion offers commands, flags, flag values such as --state and --json fields, and values from your instance such as repositories. Add the line for your shell to its startup file:
# ~/.bashrc (on macOS, ~/.bash_profile)
eval "$(tea completion bash)"
# ~/.zshrc, after compinit
autoload -U compinit && compinit
source <(tea completion zsh)
# fish
tea completion fish > ~/.config/fish/completions/tea.fish
# PowerShell profile
tea completion powershell | Out-String | Invoke-Expression
The bash script needs the bash-completion package. On macOS, install bash-completion with Homebrew for the system bash 3.2 (or bash-completion@2 for a Homebrew bash 4.2+), and use eval as above: bash 3.2 cannot source <(...). Without compinit, zsh reports command not found: compdef. tea completion <shell> --help shows these steps and how to install the script system-wide.
Man Page
The hidden command tea man can be used to generate the tea man page.
# for bash or zsh
man <(tea man)
# for fish
man (tea man | psub)
# write man page to a file
tea man --output-file ./tea.man
Compilation
Make sure you have a current Go version installed (1.27 or newer).
-
To compile the source yourself with the recommended flags & tags:
git clone https://gitea.com/gitea/tea.git # or: tea repo clone https://gitea.com/gitea/tea ;) cd tea makeNote that GNU Make (gmake on OpenBSD) is required. If you want to install the compiled program you have to execute the following command:
make installThis installs the binary into the "bin" folder inside of your GOPATH folder (
go env GOPATH). It is possible that this folder isn't in your PATH Environment Variable. -
For a quick installation without
git&make, set $version and exec:go install gitea.dev/tea@${version}
Contributing
Fork -> Patch -> Push -> Pull Request
make testrun unit testsmake vetrun checks (check the order of imports; preventing failure on CI pipeline beforehand)make buildbuilds the production CLImake docsregenerates references, man pages, and shell completions indocs/generated(not committed; built on release)- ... (for other development tasks, check the
Makefile)
Please read the CONTRIBUTING documentation, it will tell you about internal structures and concepts.
License
This project is under the MIT License. See the LICENSE file for the full license text.