gitea-tea

Files (1)

• SKILL.md

SKILL.md (first lines)

# Gitea + tea CLI

Use this skill when tasks target Gitea and the `tea` CLI, especially if the user would normally use `gh` on GitHub.

## When To Use

- User mentions Gitea, self-hosted git, forgejo-compatible flows, or `tea`
- You need CLI automation for issues, pull requests, repos, comments, or releases
- You need host-specific auth profiles (multiple Gitea instances)
- Managing Gitea Actions (secrets, variables, runners, workflow runs)
- Managing webhooks, notifications, or admin tasks

## Core Rules

1. Prefer `tea` over `gh` for Gitea targets.
2. Always scope commands to target explicitly when ambiguity exists:
   - `--repo owner/name`
   - `--login <profile>`
   - `--remote <remote-name>`
3. If command flags differ by tea version, run `tea <cmd> --help` first and follow local help text.
4. For PR/review actions, ensure local branches are pushed before create/merge operations.

## Auth Workflow

### Create login profile (token)

```bash
tea logins add --name <profile> --url https://git.example.com --token <token>
```

### Verify logins / switch default

```bash
tea logins ls
tea logins default <profile>
```

### Quick auth check

```bash
tea whoami                         # Show current user
```

### Optional env-based auth (automation)

- `GITEA_SERVER_URL`
- `GITEA_SERVER_TOKEN`
- `GITEA_SERVER_USER`
- `GITEA_SERVER_PASSWORD`

## Command Mapping (gh -> tea)

- Repo list: `gh repo list` -> `tea repos ls`
- Issue list: `gh issue list` -> `tea issues ls`
- Issue create: `gh issue create` -> `tea issues create`
- PR list: `gh pr list` -> `tea pulls ls` or `tea pr ls`
- PR create: `gh pr create` -> `tea pulls create`
- PR checkout: `gh pr checkout <n>` -> `tea pulls checkout <n>`
- Comment on PR/issue: `gh pr comment` / `gh issue comment` -> `tea comment <index> [body]`
- Release list/create: `gh release list/create` -> `tea releases ls` / `tea releases create`

## Practical Patterns

### Work on a specific repo

```bash
tea issues ls --repo owner/name --login <profile>
tea pulls ls --repo owner/name --login <profile>
```

### Create issue / PR

```bash
tea issues create --repo owner/name --title "Title" --description "Details"
tea pulls create --repo owner/name --head <branch> --title "Title" --description "Details"
```

### Review / merge PR

```bash
tea pulls review <index>
tea pulls approve <index>
tea pulls merge <index>
```

### Release workflow

```bash
tea releases create --repo owner/name --tag vX.Y.Z --title "vX.Y.Z"
tea releases assets --help
```

### Clone repo

```bash
tea clone <repo-slug> [target-dir]
tea clone gitea/tea                                 # Short form
tea clone https://git.example.com/owner/repo.git    # Full URL
```

Supports various slug formats: `owner/repo`, `host/owner/repo`, full URLs. Overrides login when host specified.

## Gitea Actions

### Repository actions (secrets, variables, runs, workflows)

```bash
tea actions secrets ls --repo owner/name
tea actions secrets create --repo owner/name <name> <value>

tea actions variables ls --repo owner/name
tea actions variables set --repo owner/name <key> <value>

tea actions runs ls --repo owner/name
tea actions runs view <run-id> --repo owner/name
tea actions runs logs <run-id> --repo owner/name

tea actions workflows ls --repo owner/name
tea actions workflows dispatch <workflow-id> --repo owner/name

From Aidas-dev/k8s-agent-skills, MIT.

More from Aidas-dev/k8s-agent-skills