chore: Add post-merge hook for automatic pnpm install#13089
Merged
kangfenmao merged 1 commit intomainfrom Feb 27, 2026
Merged
Conversation
DeJeune
approved these changes
Feb 27, 2026
kangfenmao
approved these changes
Feb 27, 2026
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
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.
What this PR does
Adds automatic
pnpm installexecution aftergit pullorgit mergeby configuring a post-merge hook via pre-commit.Why we need it and why it was done in this way
Developers often forget to run
pnpm installafter pulling changes, leading to inconsistent dependency states. This hook automatically detects changes topackage.jsonorpnpm-lock.yamland runs the install command.The following tradeoffs were made:
The following alternatives were considered: None
Breaking changes
None.
Special notes for your reviewer
Run
pnpm prepareafter merging to activate the hook.Checklist
Release note