Feature/sat 27 fix send to client option (#35)6d609615 months ago22 lines · 1.0 KB | 1 | # Issue tracker: GitHub |
| 2 | |
| 3 | Issues and PRDs for this repo live as GitHub issues. Use the `gh` CLI for all operations. |
| 4 | |
| 5 | ## Conventions |
| 6 | |
| 7 | - **Create an issue**: |
| 8 | - **Read an issue**: |
| 9 | - **List issues**: |
| 10 | - **Comment on an issue**: |
| 11 | - **Apply / remove labels**: |
| 12 | - **Close**: |
| 13 | |
| 14 | Infer the repo from `git remote -v` — `gh` does this automatically when run inside a clone. |
| 15 | |
| 16 | ## When a skill says "publish to the issue tracker" |
| 17 | |
| 18 | Create a GitHub issue. |
| 19 | |
| 20 | ## When a skill says "fetch the relevant ticket" |
| 21 | |
| 22 | Run `gh issue view <number> --comments`. |
`
gh issue create --title "..." --body "..."
`
. Use a heredoc for multi-line bodies.
`
gh issue view <number> --comments
`
, filtering comments by
`
jq
`
and also fetching labels.
`
gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'
`
with appropriate
`
--label
`
and
`
--state
`
filters.
`
gh issue comment <number> --body "..."
`
`
gh issue edit <number> --add-label "..."
`
/
`
--remove-label "..."
`
`
gh issue close <number> --comment "..."
`