ZacharyZhang-NY
9a805ae270
Constraint: Boss Windows artifacts are built on a native GitHub runner from a temporary snapshot branch Rejected: Build Boss Windows locally on Apple Silicon | docker/wine packaging is not stable on this host Confidence: medium Scope-risk: narrow Directive: This snapshot branch is transport-only and should be deleted after the Boss build is recovered locally Tested: local Boss mac build stages before snapshot creation Not-tested: remote Boss Windows packaging before workflow execution
1.0 KiB
1.0 KiB
Issue tracker: GitHub
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
Conventions
- Create an issue:
gh issue create --title "..." --body "...". Use a heredoc for multi-line bodies. - Read an issue:
gh issue view <number> --comments, filtering comments byjqand also fetching labels. - List issues:
gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'with appropriate--labeland--statefilters. - Comment on an issue:
gh issue comment <number> --body "..." - Apply / remove labels:
gh issue edit <number> --add-label "..."/--remove-label "..." - Close:
gh issue close <number> --comment "..."
Infer the repo from git remote -v — gh does this automatically when run inside a clone.
When a skill says "publish to the issue tracker"
Create a GitHub issue.
When a skill says "fetch the relevant ticket"
Run gh issue view <number> --comments.