sync-github-bug
sync-github-bug
Purpose
One-way sync of a local bug report to GitHub Issues. Auto-detects create vs update from github_issue.
github_issue present? |
Action |
|---|---|
| Absent / null | Pre-flight dedup search by bug id, then Create if no match, linking the issue as a sub-issue of its parent's issue when there is one. Writes github_issue back to the file. |
| Present | Update the existing issue (title, body, labels), reconcile open/closed state with the bug's lifecycle status. A Status History row is written only if the status transitioned. |
Difference from sync-github-task: a bug is not standalone. It hangs off a story, a task, or the bug registry, and on GitHub that relationship is a real sub-issue link. It also carries ## Status History in place of ## Change Log, and it must read files that have no frontmatter at all.
Difference from sync-jira-bug: the parent relationship is a sub-issue, not a sibling with an issue link. GitHub sub-issues carry no type constraint, so a bug nests under its parent directly; Jira would have to switch the Bug to a sub-task type to do the same, which differs per board and would cost the bug its own backlog placement and transitions. Same intent, different mechanism, because the platforms differ.