The pipelines decide what each CI job runs, and `pnpm pipeline` reports a pipeline whose script does not exist as skipped and exits 0. The task settings also control ordering and the cache keys of the remotely cached jobs. An unowned tasks.yaml could therefore turn a CI check into a no-op without code-owner review. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
20 lines
702 B
Plaintext
20 lines
702 B
Plaintext
* @zkochan
|
|
/pnpm11/pkg-manager/plugin-commands-installation/src/import/* @fireairforce
|
|
/pnpm11/reviewing/dependencies-hierarchy/* @gluxon
|
|
/pnpm11/reviewing/list/* @gluxon
|
|
/pnpm11/reviewing/plugin-commands-listing/* @gluxon
|
|
/pnpm11/reviewing/license-scanner/* @weyert
|
|
/pnpm11/reviewing/plugin-commands-licenses/* @weyert
|
|
/pnpm11/hooks/* @d3lm
|
|
|
|
# Supply-chain and CI settings, and code that runs on install
|
|
/pnpm-workspace.yaml @zkochan
|
|
/.config/pnpm/policies.yaml @zkochan
|
|
/.pnpmfile.cjs @zkochan
|
|
/.config/pnpm/patches/ @zkochan
|
|
/.config/pnpm/tasks.yaml @zkochan
|
|
|
|
# No code owner: pnpm-workspace.yaml lets this file define only the
|
|
# catalog settings and the update settings.
|
|
/.config/pnpm/catalog.yaml
|