also looking at this
feat(touch): post the checkboxes the finishing-touch flow waits on
#1424
7 files
+149
-5
| @@ -22,7 +22,7 @@ hero: | ||
| 22 | 22 | - file: "on the pull request" |
| 23 | 23 | lang: "ascii" |
| 24 | 24 | content: | |
| 25 | buddy commented on #128 | |
| 25 | buddy updated the description of #128 | |
| 26 | 26 | |
| 27 | 27 | Finishing touches — tick one and I will |
| 28 | 28 | open it as a pull request against this |
| @@ -99,9 +99,14 @@ Touches whose output is a *suggestion* rather than a commit — `simplify` and ` | ||
| 99 | 99 | |
| 100 | 100 | ## Running one |
| 101 | 101 | |
| 102 | From the thread, tick the checkbox Buddy posts. From the CLI: | |
| 102 | Tick the checkbox Buddy posts. It appends them to the pull request's | |
| 103 | description when the request is opened or marked ready — the description | |
| 104 | rather than a comment, because that is what fires the `pull_request: edited` | |
| 105 | event a tick has to be noticed by. Offering is idempotent, so a draft later | |
| 106 | marked ready does not collect a second set of boxes. | |
| 103 | 107 | |
| 104 | 108 | ```bash |
| 109 | buddy touch 128 --offer # post the checkboxes | |
| 105 | 110 | buddy touch 128 # read the ticked boxes and run them |
| 106 | 111 | buddy touch 128 --name unit-tests # run one directly |
| 107 | 112 | buddy touch 128 --test-command "bun test" |