Khải 4041a89468 ci(benchmark): skip benchmark workflows on PRs that can't affect timings (#295)
* ci(benchmark): skip benchmark workflows on PRs that can't affect timings

Both Integrated-Benchmark and Micro-Benchmark used to run on every
pull_request, even when the diff was docs-only or touched only the
npm wrapper / other workflows. Add a `paths:` allow-list so the jobs
trigger only on changes that can actually move benchmark numbers:
Rust sources, Cargo manifests / lockfile, the toolchain pin, the
shared CI actions, and the workflow file itself.

Integrated-Benchmark additionally watches `justfile` (used by
`just install` / `just integrated-benchmark`) and the registry-mock
manifest files (which decide what verdaccio serves). Micro-Benchmark
additionally watches its local `fixtures/` tarball.

Resolves https://github.com/pnpm/pacquet/issues/293.

* docs: remove unnecessary comments

Co-authored-by: Khải <hvksmr1996@gmail.com>

* ci(integrated-benchmark): trigger on fixture file changes

The benchmark workload (package.json, pnpm-lock.yaml,
pnpm-workspace.yaml under tasks/integrated-benchmark/src/fixtures/)
is embedded into the binary via include_str!. Updating any of those
files changes what the benchmark installs and therefore what it
times, so add the directory to the paths allow-list.

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-04-25 21:33:35 +02:00
Description
No description provided
MIT 354 MiB
Languages
Rust 63.2%
TypeScript 36.3%
JavaScript 0.4%