@tryarcanist/cli 0.1.403 → 0.1.405
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.
- package/README.md +3 -1
- package/dist/index.js +70 -70
- package/package.json +4 -2
package/README.md
CHANGED
|
@@ -23,7 +23,9 @@ arcanist onboard --json
|
|
|
23
23
|
arcanist onboard owner/repo --pr https://github.com/owner/repo/pull/123 --json
|
|
24
24
|
```
|
|
25
25
|
|
|
26
|
-
Follow `command` to resume and `repository.nextAction` for setup interventions. `setup_pending` can be polled every five seconds. `repository_ready` means setup finished but the first review is still unverified: pass an existing PR with `--pr`. `review_pending` resumes the same review. Cancelled, rejected, or missing saved requests are cleared so the next invocation can retry. After new commits or an incomplete result, use `--pr <url> --restart-review` once to request verification again; resume with the returned command, which omits that flag. Only `complete` with `reviewVerified: true` proves a conclusive review of the returned `headSha`; findings do not make onboarding fail. `review_needs_attention` requires inspecting the incomplete result. Do not create a PR or change its code merely to finish onboarding.
|
|
26
|
+
Follow `command` to resume and `repository.nextAction` for setup interventions. `setup_pending` can be polled every five seconds. `repository_ready` means setup finished but the first review is still unverified: pass an existing PR with `--pr`. `review_pending` resumes the same review. The CLI saves a request key before starting it, so retrying after a lost response recovers that review even after it finishes. Concurrent commands use the same saved request; if another command still holds the lock, the CLI asks you to retry shortly. Cancelled, rejected, or missing saved requests are cleared so the next invocation can retry. After new commits or an incomplete result, use `--pr <url> --restart-review` once to request verification again; resume with the returned command, which omits that flag. Only `complete` with `reviewVerified: true` proves a conclusive review of the returned `headSha`; findings do not make onboarding fail. `review_needs_attention` requires inspecting the incomplete result. Do not create a PR or change its code merely to finish onboarding.
|
|
27
|
+
|
|
28
|
+
If a connection drops during sign-in, rerun the command. The same approval recovers the same token until its ten-minute server expiry; revoked tokens cannot be recovered. Concurrent terminal processes share the approval, and saved credentials are replaced atomically with private permissions.
|
|
27
29
|
|
|
28
30
|
Each repository needs its own environment for reviews. Appearing as a dependency in another repository’s workspace does not make it ready; onboarding prepares it separately.
|
|
29
31
|
|