feat: implement metadata catalog database management
This commit is contained in:
@@ -0,0 +1,7 @@
|
||||
# Domain Docs
|
||||
|
||||
This is a single-context repository.
|
||||
|
||||
Before exploring, read `CONTEXT.md` at the repository root and the relevant decisions in
|
||||
`docs/adr/`. Use the project's terminology from `CONTEXT.md` in issue titles, proposals, and
|
||||
tests. Surface conflicts with an ADR instead of silently overriding it.
|
||||
@@ -0,0 +1,28 @@
|
||||
# Issue tracker: Gitea
|
||||
|
||||
Issues and specs for this repository live in the self-hosted Gitea repository:
|
||||
`https://git.tylconsulting.it/mptyl/ThothII`.
|
||||
|
||||
## Conventions
|
||||
|
||||
- **Create an issue**: use the repository's Gitea web UI, or the Gitea REST API when an
|
||||
authenticated token with issue scope is available.
|
||||
- **Read and list issues**: use the Gitea web UI or authenticated API; include labels and comments.
|
||||
- **Apply or remove labels**: use the issue's label controls or the Gitea API.
|
||||
- **Comment and close**: use the issue page or the Gitea API.
|
||||
- Do not use `gh issue ...` for this repository: the `github` remote is a mirror, not the canonical
|
||||
issue tracker.
|
||||
|
||||
## Repository identity
|
||||
|
||||
- Canonical Git remote: `origin` → `https://git.tylconsulting.it/mptyl/ThothII.git`
|
||||
- GitHub mirror: `github` → `https://github.com/mptyl/ThothII.git`
|
||||
- Canonical issue URL: `https://git.tylconsulting.it/mptyl/ThothII/issues`
|
||||
|
||||
## When a skill says “publish to the issue tracker”
|
||||
|
||||
Create an issue in the canonical Gitea repository.
|
||||
|
||||
## When a skill says “fetch the relevant ticket”
|
||||
|
||||
Read the referenced issue in the canonical Gitea repository.
|
||||
@@ -0,0 +1,19 @@
|
||||
# Triage Labels
|
||||
|
||||
The skills speak in terms of five canonical triage roles. This file maps those roles to the labels
|
||||
used in the canonical Gitea issue tracker.
|
||||
|
||||
| Label in mattpocock/skills | Label in Gitea | Meaning |
|
||||
| --- | --- | --- |
|
||||
| `needs-triage` | `needs-triage` | Maintainer needs to evaluate this issue |
|
||||
| `needs-info` | `needs-info` | Waiting on reporter for more information |
|
||||
| `ready-for-agent` | `ready-for-agent` | Fully specified, ready for AFK agent work |
|
||||
| `ready-for-human` | `ready-for-human` | Requires human implementation |
|
||||
| `wontfix` | `wontfix` | Will not be actioned |
|
||||
|
||||
Issue type labels:
|
||||
|
||||
| Label in Gitea | Meaning |
|
||||
| --- | --- |
|
||||
| `bug` | Something is not working |
|
||||
| `enhancement` | New feature or request |
|
||||
Reference in New Issue
Block a user