You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
Fadlika Dita Nurjanto
fadlikadn
Seasoned Software Engineer in full-stack development and cloud infrastructure using TypeScript, NodeJS, PHP
How to do a "dry run" of a git merge to see what would happen without actually committing to it
title
How to do a "dry run" of a git merge to see what would happen without actually committing to it.
tags
git
github
git merge
git diff
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.
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
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
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