@taqwright/lime-cli 0.16.0 → 0.18.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.
Files changed (3) hide show
  1. package/README.md +15 -4
  2. package/dist/index.js +176 -156
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -331,9 +331,13 @@ Taqwright for a copy) is a ready-made GitHub Actions workflow: a developer comme
331
331
  ```
332
332
 
333
333
  on a pull request in your **app** repo, and the workflow builds that PR's app, records the
334
- flow on a cloud device, adapts the test into your **test-suite** repo, verifies it passes,
335
- and opens a pull request there linking back. LIME holds no GitHub credential — the runner
336
- already has yours.
334
+ flow on a cloud device, and hands the recording to your **test-suite** repo's own workflow
335
+ (`taqwright-automate.yml`, the one the LIME console's Automate button starts) with
336
+ `lime-cli pr automate`. That workflow adapts the test, pushes it with its own `GITHUB_TOKEN` and
337
+ has the **Taqwright GitHub App** open the pull request; `lime-cli pr wait` waits for it so the
338
+ reply links it. The app repo needs **no credential for the test repo** — no GitHub App of your
339
+ own and no PAT; the test repo is the one bound to the LIME project (Integrations → GitHub →
340
+ Automation setup binds it and adds the workflow).
337
341
 
338
342
  Where `lime-cli pr` has commented with **suggested tests**, pick one by number instead of typing
339
343
  a goal:
@@ -343,7 +347,14 @@ a goal:
343
347
  ```
344
348
 
345
349
  The goal comes from LIME's analysis of that pull request, never from the comment. A suggestion
346
- behind a feature flag is held back until a test user for it exists. **Every reply on the pull
350
+ behind a feature flag is held back until a test user for it exists.
351
+
352
+ **Several at once, in parallel.** On Taqwright for GitHub with **parallel slots**,
353
+ `docs/github/automate-parallel.yml` takes `/automate 1,3,4`. It records the tests side by side, one
354
+ job per slot, each with its own token (`LIME_CI_TOKEN_1`, `LIME_CI_TOKEN_2`, … from Settings →
355
+ Access → Parallel slots, plus `vars.LIME_SLOTS`). It then adapts and verifies them one at a time in
356
+ one checkout, so shared page objects are written once, and opens **one** test pull request with a
357
+ commit per test that passed. Use it instead of `automate.yml`, not beside it. **Every reply on the pull
347
358
  request** comes from the **Taqwright GitHub App**: the 👀, "Automating…", and the result. The
348
359
  workflow never comments with its own token, so the templates only need `pull-requests: read`.
349
360