[WIP] Configure pnpm-lock.yaml merge driver #59
Closed
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.
Configure pnpm-lock.yaml Merge Driver
Setting up a custom Git merge driver to automatically handle merge conflicts in pnpm-lock.yaml by regenerating the file using
pnpm install.Changes:
.gitattributesfile with merge driver configuration for pnpm-lock.yamlImplementation Details:
.gitattributes: Specifies thatpnpm-lock.yamlshould use thepnpm-mergecustom merge driverpackage.json: Added postinstall script that runs:git config merge.pnpm-merge.name "pnpm-lock.yaml merge driver"git config merge.pnpm-merge.driver "pnpm install"CONTRIBUTING.md: Added documentation explaining the merge driver featureHow It Works:
When a merge conflict occurs in
pnpm-lock.yaml, Git will automatically runpnpm installto regenerate the lock file instead of creating merge conflict markers. This ensures the lock file stays consistent and valid.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.