@bensandee/tooling 0.89.1 → 0.91.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.
- package/README.md +1 -1
- package/dist/bin.mjs +1106 -568
- package/package.json +4 -4
- package/tooling.schema.json +9 -4
package/README.md
CHANGED
|
@@ -57,7 +57,7 @@ The `--add` flag appends extra checks (must be defined in `package.json`):
|
|
|
57
57
|
tooling checks:run --add e2e
|
|
58
58
|
```
|
|
59
59
|
|
|
60
|
-
**Coverage is branch-aware by default.** With neither coverage flag, the `test` step runs via `pnpm run test:coverage` (producing `coverage/coverage-summary.json` for the `coverage:*` commands) **only on the repo's default branch** -- PR and feature-branch runs skip the v8 instrumentation cost automatically. The current branch is read from `GITHUB_REF` / `GITHUB_REF_NAME` (set by GitHub _and_ Forgejo Actions), falling back to `git rev-parse --abbrev-ref HEAD` for local runs; tag and pull-request refs count as non-default. The default branch is `.tooling.json#defaultBranch` if set, otherwise detected via `git symbolic-ref refs/remotes/origin/HEAD`, otherwise `main`.
|
|
60
|
+
**Coverage is branch-aware by default.** With neither coverage flag, the `test` step runs via `pnpm run test:coverage` (producing `coverage/coverage-summary.json` for the `coverage:*` commands) **only on the repo's default branch** -- PR and feature-branch runs skip the v8 instrumentation cost automatically. The current branch is read from `GITHUB_REF` / `GITHUB_REF_NAME` (set by GitHub _and_ Forgejo Actions), falling back to `git rev-parse --abbrev-ref HEAD` for local runs; tag and pull-request refs count as non-default. The default branch is `.tooling.json#defaultBranch` if set, otherwise detected via `git symbolic-ref refs/remotes/origin/HEAD`, otherwise `main`. The same field is the branch the generated CI workflow triggers on and the gate every release step and history record in `ci.yml` and `release.yml` checks, so a repo on a branch other than `main` releases from it; generated output uses `main` when the field is unset.
|
|
61
61
|
|
|
62
62
|
Explicit flags always win, regardless of branch:
|
|
63
63
|
|