mirror of
https://gitverse.ru/kpa39l/vesti.git
synced 2026-09-29 09:55:03 +00:00
kpa39l
63 lines
2.7 KiB
Markdown
63 lines
2.7 KiB
Markdown
# Issue Tracker
|
|
|
|
**Tracker:** Gitea (self-hosted, https://gitea.nixg.ru)
|
|
**Repository:** `estorozhenko/vesti` (mirror from gitverse.ru/kpa39l/vesti)
|
|
**Web UI:** https://gitea.nixg.ru/estorozhenko/vesti
|
|
|
|
This is a custom ("Other") tracker configuration for the Matt Pocock engineering skills (`to-tickets`, `to-spec`, `triage`). Gitea is not natively supported by `/setup-matt-pocock-skills`, so the workflow is recorded here as freeform prose.
|
|
|
|
## How to publish issues
|
|
|
|
Use the **`tea` CLI** (v0.16.0, at `~/.local/bin/tea`) with the login **`gitea.nixg-full`**:
|
|
|
|
```bash
|
|
export PATH="$HOME/.local/bin:$PATH"
|
|
|
|
# Create an issue
|
|
tea issues create --login gitea.nixg-full --repo estorozhenko/vesti \
|
|
--title "Ticket title" \
|
|
--description "Ticket body (use the to-tickets per-ticket template)" \
|
|
--labels "ready-for-agent"
|
|
|
|
# List issues
|
|
tea issues list --login gitea.nixg-full --repo estorozhenko/vesti -o simple
|
|
|
|
# Show one issue (with comments)
|
|
tea issues --login gitea.nixg-full --repo estorozhenko/vesti 42 --comments
|
|
|
|
# Add a comment
|
|
tea comment --login gitea.nixg-full --repo estorozhenko/vesti 42 "comment"
|
|
|
|
# Close / reopen
|
|
tea issues close --login gitea.nixg-full --repo estorozhenko/vesti 42
|
|
```
|
|
|
|
**Alternative:** the `gitea` MCP server (gitea-mcp, 72 tools) is configured in Hermes `mcp_servers.gitea` — same instance, same token. Prefer MCP tools in agent sessions, `tea` for quick shell checks.
|
|
|
|
## Repository and credentials
|
|
|
|
- Instance: `https://gitea.nixg.ru` (API v1.26.2, external VPS 5.129.217.146)
|
|
- Owner/repo: `estorozhenko/vesti` (mirror of `https://gitverse.ru/kpa39l/vesti.git`, issues enabled: yes)
|
|
- Login (tea): `gitea.nixg-full` — token `hermes-mcp-full`
|
|
- Token source: `/opt/hermes/.hermes/secrets/git-tokens.env` (`GITEA_NIXG_TOKEN`); also in Hermes `config.yaml` → `mcp_servers.gitea` env `GITEA_TOKEN`.
|
|
- Git push: to the **origin** (gitverse.ru) via SSH key `/home/estorozhenko/.ssh/gitverse` — the Gitea repo is a read-only mirror and is NOT the push target.
|
|
|
|
## Triage labels (created)
|
|
|
|
| Label | Color | ID |
|
|
|---|---|---|
|
|
| `needs-triage` | `#e11d21` | 6 |
|
|
| `needs-info` | `#fbca04` | 7 |
|
|
| `ready-for-agent` | `#0e8a16` | 8 |
|
|
| `ready-for-human` | `#006b75` | 9 |
|
|
| `wontfix` | `#ffffff` | 10 |
|
|
|
|
Use `ready-for-agent` for tickets published by `to-tickets`.
|
|
|
|
## Blocking edges
|
|
|
|
Gitea has no native issue-blocking links. Follow the `to-tickets` rule for trackers without native blocking: publish tickets in dependency order (blockers first), and set each ticket's **"Blocked by"** section to the blocking issues' real identifiers (e.g. `#12`, `#13`).
|
|
|
|
## Scope
|
|
|
|
Tickets for the VESTI project live in `estorozhenko/vesti`. Local fallback: `.scratch/<feature>/issues/` in this project when no Gitea write access. |