chore: gitignore pnpm's build-approval state (pnpm-workspace.yaml) - #5
Open
warnes wants to merge 1 commit into
Open
chore: gitignore pnpm's build-approval state (pnpm-workspace.yaml)#5warnes wants to merge 1 commit into
warnes wants to merge 1 commit into
Conversation
Running `pnpm install` fresh prompts to approve esbuild's postinstall script (tsup's dependency); approving it writes the decision into pnpm-workspace.yaml. That's a machine-local trust decision, not portable project config, and shouldn't get committed by whichever contributor happens to approve it first. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Small, independent housekeeping fix found while setting up a fresh clone for #1/#2/#3.
Running
pnpm installprompts to approve esbuild's postinstall script (a dependency of tsup); approving it (pnpm approve-builds) writes the decision intopnpm-workspace.yaml, which pnpm auto-creates if it doesn't already exist. That's a machine-local trust decision, not portable project config — whichever contributor approves it first shouldn't end up committing it for everyone else.