1.2 KiB
Provider-neutral tracker automation
Use tracker for normal issue and pull-request automation. It owns the high-level operation, prerequisite checks, normalization, bounded retry policy, and JSON protocol; it delegates credentials and provider commands to gh, glab, or tea.
tracker --provider gitea issue get 16
TRACKER_PROVIDER=gitlab tracker issue list --state open --label ready-for-agent
tracker pr get 42 --diff
Provider selection is explicit CLI flag, then TRACKER_PROVIDER, then the origin remote. Always choose issue or pr explicitly for reads and writes. Use resolve-reference only for an intentionally ambiguous bare number.
Parse ok and error.code; do not parse provider output or issue exploratory retries. The library (from tracker import Tracker) returns the same envelope as the CLI. RecordingRunner provides the fake subprocess seam for tests.
Provider-specific capability and fallback references remain in docs/agents/issue-tracker.md and the setup templates. They are not the normal execution path. Wayfinding relationships may use native provider APIs where available and task-list/body or note fallbacks otherwise; the result's details identifies the relationship mode.