skills.rest
Aidas-dev
Aidas-devCOMMUNITY
Explore all skills by this author →
GitHub

gitea-tea

Automate Gitea repository, issue, pull request, and release workflows using the tea CLI.

4|2|Updated Jun 1, 2026
Search Tags:#pull requests#webhooks#gitea#self-hosted git#ci automation#tea cli#git forge
One-click install
npx skills add https://github.com/Aidas-dev/k8s-agent-skills --skill gitea-tea-aidas-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitea-tea
Source: https://github.com/Aidas-dev/k8s-agent-skills/tree/main/skills/gitea-tea
Command: npx skills add https://github.com/Aidas-dev/k8s-agent-skills --skill gitea-tea-aidas-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working with self-hosted Gitea instances lacks the polished CLI tooling that GitHub users enjoy with gh, forcing users to click through web UIs or write raw API calls for routine tasks like managing issues, pull requests, releases, webhooks, and Actions runners. ## Core Features & Use Cases - Full repo lifecycle via tea CLI: Manage logins, repositories, issues, pull requests, comments, and releases with explicit --repo and --login scoping for multi-instance setups. - Gitea Actions and webhooks automation: Manage Actions secrets, variables, workflow runs, and host-mode runners on Talos, plus create org- or repo-level webhooks for Slack, Discord, and other services. - Use Case: You maintain multiple self-hosted Gitea instances and need to review and merge a pull request from the terminal. Use this Skill to select the correct login profile, list open PRs, review, approve, and merge without leaving your shell. ## Quick Start Use the gitea-tea skill to list all open pull requests in my repository and then create a new issue titled "Bug in login flow" with a short description.

Frequently Asked Questions about gitea-tea

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use the tea CLI with Gitea instead of gh?▼

Map gh commands directly to tea equivalents: gh repo list becomes tea repos ls, gh pr create becomes tea pulls create, and gh issue list becomes tea issues ls. Always scope commands with --repo owner/name and --login profile when multiple instances exist.

How do I authenticate tea CLI with multiple Gitea instances?▼

Run tea logins add --name <profile> --url https://git.example.com --token <token> for each instance, then verify with tea logins ls. Pass --login <profile> on every command to avoid accidentally using the default profile.

Can Gitea Actions runners work on Talos Linux without Docker?▼

Yes, use a host-mode runner by setting the GITEA_RUNNER_LABELS value with a :host suffix such as ubuntu-latest:host. Job steps run as processes inside the runner container, so the image must include tools like curl and git.

Why does tea pulls create fail to create my pull request?▼

The tea CLI does not push your branch automatically, so run git push -u origin <branch> before creating the PR. Also verify you are targeting the correct repository with --repo and the right instance with --login.

How do I avoid leaking webhook secrets when using tea?▼

Passing --secret on the command line can expose the value in shell history. Use --secret-stdin or environment variables instead when creating webhooks with tea webhooks create.

Related Skills

Explore More Software Engineering Skills→
redbananastudiosredbananastudios

shopify-setup

Set up authenticated Shopify Admin API access with a custom app and GraphQL verification.

Community
Intermediate
doleval013doleval013

deploy

Automate production deployments via GitOps with GitHub Actions and ArgoCD.

Community
Advanced
erfianugraherfianugrah
1

ci-workflows

Pin GitHub Actions and Gitea Actions workflow versions with YAML compatibility rules.

Community
Intermediate
hay-kothay-kot
11

tea

Manage Gitea/Forgejo repositories, pull requests, and issues via the tea CLI.

Community
Intermediate