GitHub Issue Bridge
Context
This workflow explains how issue creation is automated from repository context without relying on manual UI steps.
Details
Bridge flow:
1. Build a normalized issue payload (title, body, labels).
2. Resolve repository context from git remote.
3. Validate authentication and required inputs.
4. Create issue through automation layer.
5. Persist state and append audit trace.
Operational guarantees: - deterministic payload structure; - explicit failure messages for missing token or unsupported remotes; - dry-run path available for safe validation before production usage.
Where to look during troubleshooting:
- runtime state: logs/github_issue_bridge_state.json;
- audit events: logs/github_issue_audit.jsonl.
Links
- ../02_data-models/storage-contracts.md
- ../../../scripts/create_github_issue.py
- ../../../src/github_issue_automation.py
- Runtime state reference:
logs/github_issue_bridge_state.json(operational file, not versioned) - Audit trail reference:
logs/github_issue_audit.jsonl(operational file, not versioned)