issue-core/issue_core/__init__.py
tegwick bbbc5819c5
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Build and Publish Container Image / build-and-push (push) Successful in 54s
docs: restructure SCOPE.md as shipped inventory vs product boundary
Rewrite SCOPE to separate what issue-core provides today (models, backends,
CLI, REST, sync, deploy) from in-scope growth and out-of-scope fleet work.
Align package __init__ description with the connector role.
2026-07-21 23:52:08 +02:00

16 lines
592 B
Python

"""
issue-core — external issue-tracker connector
Backend-agnostic CLI, library, and optional REST surface for operating on
third-party issue trackers (Gitea/Forgejo, local SQLite). Not the origin of
fleet work records (see INTENT.md / SCOPE.md).
Shipped:
- Unified issue model and IssueBackend plugin architecture
- Local SQLite + Gitea 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"