Verify latest release

• I verified that the issue exists in the latest pnpm release

pnpm version

No response

Which area(s) of pnpm are affected? (leave empty if unsure)

CLI

Link to the code that reproduces this issue or a replay of the bug

No response

Reproduction steps

Our team is currently migrating a ~50 package monorepo into a pnpm workspace. (each package is a self-contained node microservice)
We are doing an incremental migration where we would migrate service by service into the workspace.

Describe the Bug

The big problem we ran into was that as soon we had the pnpm-workspace.yml in a parent directory, the package management commands would affect the workspace even if the current directory was not in the workspace.

This was a big problem because this put the incremental migration approach at risk.
After some googling, we found this discussion post and it solved our problem exactly.
But we could not find a reference to this in the pnpm documentation. Neither the docs nor in the help reference this command.

Expected Behavior

A mention of the --ignore-workspace option in the help of

• add
• remove
• update

proposed documentation:
stolen from: https://github.com/pnpm/pnpm/releases/tag/v6.25.0

--ignore-workspace         When used, pnpm ignores any workspace configuration found in the current or parent directories.

Which Node.js version are you using?

v20.11.0

Which operating systems have you used?

• macOS
• Windows
• Linux

If your OS is a Linux based, which one it is? (Include the version if relevant)

No response