Prefer Forgejo as the self-hosted forge product. Keep Gitea only as the Gitea-compatible API identifier (module backends/gitea, type string gitea). FORGEJO_TOKEN is preferred; GITEA_* remains a deprecated alias. INTENT/SCOPE quote ACT-ADR-005: issue-core is not the fleet ops claim queue. Connector docs describe repo work record → hub index → optional Forgejo projection, not activity-core → issue-core → harness. Assistant: grok Assistant-Session: 01a09dc6-3f0d-7c93-8b11-8e83c0623d49
16 lines
613 B
Python
16 lines
613 B
Python
"""
|
|
issue-core — external issue-tracker connector
|
|
|
|
Backend-agnostic CLI, library, and optional REST surface for operating on
|
|
third-party issue trackers (Forgejo via Gitea-compatible API, local SQLite).
|
|
Not the origin of fleet work records (see INTENT.md / SCOPE.md).
|
|
|
|
Shipped:
|
|
- Unified issue model and IssueBackend plugin architecture
|
|
- Local SQLite + Forgejo backends; bidirectional sync CLI
|
|
- CLI (`issue` / `issue-core`) and optional FastAPI REST (`issue serve`)
|
|
"""
|
|
|
|
__version__ = "0.2.1"
|
|
__author__ = "Coulomb / MarkiTect Project"
|
|
__description__ = "External issue-tracker connector with plugin backends"
|