Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Here's how to resolve a conflict that occurs during the git merge process when collaborating on a project with a team member. #239

Open
MinWook6457 opened this issue Mar 19, 2025 · 0 comments

Comments

@MinWook6457
Copy link

MinWook6457 commented Mar 19, 2025

Let's assume there are master branch, a branch, and b branch.

If branch a sends a pull request to the master branch and master merges the branch, a conflict may occur when branch b pushes. At this time, branch b is working on a feature.

Action tips for branch b

git stash

git stash is a Git command that temporarily saves the current working changes and restores the working directory to a clean state.

In other words, it allows you to store uncommitted changes and apply them later when needed.

git pull origin master
git stash pop

git stash pop applies the most recent stashed changes and removes them from the stash list.

If you go through the above process, the commit time in git staging will match, so there will be no conflict.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant