@staff0rd/assist 0.913.0 → 0.914.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -56,7 +56,7 @@ If `$ARGUMENTS` contains `--batch`, collect every decision before changing anyth
56
56
 
57
57
  1. For each thread, display it, analyse it and ask the user with AskUserQuestion exactly as in steps 1–3, recording their choice and your recommended fix. Do not edit any file, commit, reply or resolve anything until every thread has a decision.
58
58
  2. Once every thread has a decision, implement each **Address** thread in turn and run `/commit` after each — one commit per thread — noting its SHA.
59
- 3. Run `git push` once, then run `assist prs fixed <comment-id> <sha>` for each addressed thread with the SHA of the commit that addressed it, and `assist prs wontfix <comment-id> "<reason>"` for each **Do not address** thread as in step 4. Leave skipped threads untouched.
59
+ 3. Run `assist prs fixed <comment-id> <sha>` for each addressed thread with the SHA of the commit that addressed it — the first one pushes every commit, so do not run `git push` yourself — and `assist prs wontfix <comment-id> "<reason>"` for each **Do not address** thread as in step 4. Leave skipped threads untouched.
60
60
 
61
61
  ## Auto mode
62
62
 
@@ -66,7 +66,7 @@ If `$ARGUMENTS` contains `--auto`, process the threads without asking the user,
66
66
  - **Address**: implement the fix and run `/commit` — one commit per thread — noting the SHA. Do not push yet and do not run `assist prs fixed` yet.
67
67
  - **Do not address**: run `assist prs wontfix <comment-id> "<reason>"` as in step 4.
68
68
  2. If you cannot confidently decide on a thread — the comment is unclear, the fix is risky or large, or reasonable people would disagree — put that one thread to the user with AskUserQuestion exactly as in step 3, act on their choice as above, then continue automatically with the next thread.
69
- 3. Once every thread has been processed, run `git push` once, then run `assist prs fixed <comment-id> <sha>` for each addressed thread with the SHA of the commit that addressed it.
69
+ 3. Once every thread has been processed, run `assist prs fixed <comment-id> <sha>` for each addressed thread with the SHA of the commit that addressed it — the first one pushes every commit, so do not run `git push` yourself.
70
70
  4. Finish with a closing summary listing each thread and its outcome, calling out any thread that was skipped so the user can revisit it.
71
71
 
72
72
  ## Bodies containing markdown
@@ -3,8 +3,8 @@
3
3
  "assist@staff0rd.github.io": {
4
4
  "updates": [
5
5
  {
6
- "version": "0.897.0",
7
- "update_link": "https://github.com/staff0rd/assist/releases/download/v0.897.0/assist-extension.xpi"
6
+ "version": "0.913.0",
7
+ "update_link": "https://github.com/staff0rd/assist/releases/download/v0.913.0/assist-extension.xpi"
8
8
  }
9
9
  ]
10
10
  }