| title | tags | ||||
|---|---|---|---|---|---|
How to do a "dry run" of a git merge to see what would happen without actually committing to it. |
|
Example: You have a local project, and you're on the local branch called dev. You haven't started working yet, but there may have been other activity since you originally cloned the remote dev branch, and you want to see how your branch compares to the remote dev branch so you can get in sync before starting to code - but you don't want to just git pull and risk conflicts, or losing info.