generated from coulomb/repo-seed
Update README.md
This commit is contained in:
24
README.md
24
README.md
@@ -1,3 +1,23 @@
|
|||||||
# repo-seed
|
# Issue Facade - Universal CLI for Issue Tracking
|
||||||
|
|
||||||
A git repository template to bootstrap coulomb projects from.
|
A convenient command-line facade that provides a unified interface to the repository's main issue tracker, regardless of which backend system is actually being used.
|
||||||
|
|
||||||
|
## Purpose
|
||||||
|
|
||||||
|
The **Issue Facade** acts as a convenient CLI wrapper that automatically detects and interfaces with whatever issue tracking system is configured for the current repository. This means you get a consistent, intuitive command-line experience whether your project uses:
|
||||||
|
|
||||||
|
- GitHub Issues
|
||||||
|
- GitLab Issues
|
||||||
|
- Gitea Issues
|
||||||
|
- JIRA
|
||||||
|
- Local SQLite storage
|
||||||
|
- Any other supported backend
|
||||||
|
|
||||||
|
## Philosophy
|
||||||
|
|
||||||
|
Rather than learning different commands and workflows for each issue tracking system, the Issue Facade provides:
|
||||||
|
|
||||||
|
- **One CLI to rule them all**: Same commands work across all backends
|
||||||
|
- **Repository-aware**: Automatically detects the relevant issue tracker for your repo
|
||||||
|
- **Offline capability**: Local SQLite fallback when remote systems are unavailable
|
||||||
|
- **Seamless sync**: Keep local and remote issue trackers synchronized
|
||||||
Reference in New Issue
Block a user