-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Resolving PR merge conflicts for "common config rush pnpm‐lock.yaml"
Jeremy Meng edited this page Mar 13, 2025
·
7 revisions
Here's the recommended process to resolve merge conflicts of common/config/rush/pnpm-lock.yaml in your pull request (assuming your upstream remote is named "upstream"):
git fetch upstreamgit merge --no-edit upstream/main- Use your favorite IDE, editor, or Git Client to resolve conflicts for files other than
common/config/rush/pnpm-lock.yaml -
git checkout upstream/main -- common/config/rush/pnpm-lock.yamlunder the project root rush updategit add common/config/rush/pnpm-lock.yaml- Commit the merge
- Push the commit to your pull request branch, for example,
git push originassuming "origin" is remote name for your fork
Step 4) to 6) can be combined and enhanced to run under any directory under the repo if you are using a *NIX environment:
git checkout upstream/main `git rev-parse --show-toplevel`/common/config/rush/pnpm-lock.yaml && rush update && git add `git rev-parse --show-toplevel`/common/config/rush/pnpm-lock.yaml