You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
github-issues tracker adapter — GitHub Issues as the tracker of
record: waybill sync-plan --tracker github-issues. Keys are GitHub's
own cross-repo syntax (owner/repo#15), derived purely from the issue
URL leaf; the conformance kit gained a matching derivation check (a
composed key passes only when re-deriving it from the verbatim URL leaf
reproduces it exactly) and adapters may now declare their tracker's own keyPattern — the metering branch pattern is deliberately untouched.
Labels map to work_type, milestones to sprint, not_planned
closures are dropped as cancelled work, PR rows from the REST /issues
endpoint are skipped, and points stays null (GitHub has no estimates;
a point scale is never invented). Both the gh CLI and REST payload
shapes are accepted. Own-data scoping keeps unassigned issues and drops
issues assigned only to someone else.
Closing-keyword linkage — MergedChange gains closes:
"Fixes #12" in a PR body, MR description, or commit body now pairs the
change with its tracker item (GitHub's actual linkage mechanism —
title/branch pattern matching alone was structurally blind to it).
Keyword-per-reference grammar mirrors GitHub exactly; bare #15 expands
against the change's own repo. git-local now captures commit bodies and
treats a squash-merged commit carrying a closing ref as a merged change,
so linear-history GitHub-flow repos get receipts too. The conformance
kit verifies every closes ref against a closing keyword in the raw
payload.