* docs: move website documentation into the pnpm repository * docs: keep v11 and v12 documentation beside their implementations * docs(pnpr): keep registry documentation beside its implementation * ci: classify product documentation as documentation changes * test: cover product documentation in Rust CI exclusions * ci: isolate documentation publishing and support manual sync * test: make dependency status fixture timestamps deterministic
841 B
841 B
id, title
| id | title |
|---|---|
| patch-commit | pnpm patch-commit <path> |
Generate a patch out of a directory and save it (inspired by a similar command in Yarn).
This command will compare the changes from path to the package it was supposed to patch, generate a patch file, save the a patch file to patchesDir (which can be customized by the --patches-dir option), and add an entry to patchedDependencies.
Usage:
pnpm patch-commit <path>
pathis the path to a modified copy of the patch target package, it is usually a temporary directory generated bypnpm patch.
Options
---patches-dir <patchesDir>
The generated patch file will be saved to this directory. By default, patches are saved to the patches directory in the root of the project.