Skip to main content
add what to do after git stash pop
Source Link
prayagupadhyay
  • 30.9k
  • 14
  • 160
  • 194

This normally happens when you git commit and try to git push changes before git pulling on that branch x where someone else has already made changes.

The normal flow would be as below,

STEP 1: git stash your local uncommitted changes on that branch.

STEP 2: git pull origin branch_name -v to pull and mergepull and merge to locally commitedcommitted changes on that branch, give the merge some message, and fix conflicts if any. (give this merge some message, and fix conflicts if any.)

STEP 3: git stash pop the stashed changes. (Then you can make commits on popped files if you want or push already committed changes (STEP4) first and make new commit to files later.)

STEP 4: git push origin branch_name -v the merged changes.

Replace branch_name with master (for master branch).

This normally happens when you git commit and try to git push changes before git pulling on that branch x.

The normal flow would be as below,

STEP 1: git stash your local changes on that branch.

STEP 2: git pull origin branch_name -v to pull and merge to locally commited changes on that branch, give the merge some message, and fix conflicts if any.

STEP 3: git stash pop the stashed changes.

STEP 4: git push origin branch_name -v the merged changes.

Replace branch_name with master (for master branch).

This normally happens when you git commit and try to git push changes before git pulling on that branch x where someone else has already made changes.

The normal flow would be as below,

STEP 1: git stash your local uncommitted changes on that branch.

STEP 2: git pull origin branch_name -v to pull and merge to locally committed changes on that branch (give this merge some message, and fix conflicts if any.)

STEP 3: git stash pop the stashed changes (Then you can make commits on popped files if you want or push already committed changes (STEP4) first and make new commit to files later.)

STEP 4: git push origin branch_name -v the merged changes.

Replace branch_name with master (for master branch).

Copy edited (e.g. ref. <http://english.stackexchange.com/questions/4645/is-it-ever-correct-to-have-a-space-before-a-question-or-exclamation-mark#comment206109_4645>).
Source Link
Peter Mortensen
  • 31.3k
  • 22
  • 109
  • 132

This normally happens when you git commit and try to git push changes before git pulling on that branch x.

NormalThe normal flow would be as below,

STEP 1  :  git stash your local changes on that branch.

STEP 2  : git pull origin branch_name -v to pull and merge to locally commited changes on that branch, give the merge some message, and fix conflicts if any.

STEP 3  : git stash pop the stashed changes.

STEP 4  : git push origin branch_name -v the merged changes.

Replace branch_name with with master (for master branch).Replace branch_name with master (for master branch).

This normally happens when you git commit and try to git push changes before git pulling on that branch x.

Normal flow would as below,

STEP 1  :  git stash your local changes on that branch

STEP 2  : git pull origin branch_name -v to pull and merge to locally commited changes on that branch, give the merge some message, fix conflicts if any

STEP 3  : git stash pop the stashed changes

STEP 4  : git push origin branch_name -v merged changes

Replace branch_name with with master (for master branch).

This normally happens when you git commit and try to git push changes before git pulling on that branch x.

The normal flow would be as below,

STEP 1: git stash your local changes on that branch.

STEP 2: git pull origin branch_name -v to pull and merge to locally commited changes on that branch, give the merge some message, and fix conflicts if any.

STEP 3: git stash pop the stashed changes.

STEP 4: git push origin branch_name -v the merged changes.

Replace branch_name with master (for master branch).

refactor just for readability
Source Link
prayagupadhyay
  • 30.9k
  • 14
  • 160
  • 194

This normally happens when you git commit and try to git push changes before git pulling on that branch x.

Normal flow would as below,

STEP 1

`git stash` your local changes on that branch

STEP 2

`git pull origin branchname -v` to pull and merge to locally commited changes on that branch, give the merge some message, fix conflicts if any

STEP 3

`git stash pop` stash changes

STEP 4

STEP 1 : git stash your local changes on that branch

`git push origin branchname -v` merged changes

STEP 2 : git pull origin branch_name -v to pull and merge to locally commited changes on that branch, give the merge some message, fix conflicts if any

Replace branchname with withSTEP 3 : mastergit stash pop forthe masterstash branch.ed changes

STEP 4 : git push origin branch_name -v merged changes

Replace branch_name with with master (for master branch).

This normally happens when you git commit and try to git push changes before git pulling on that branch x.

Normal flow would as below,

STEP 1

`git stash` your local changes on that branch

STEP 2

`git pull origin branchname -v` to pull and merge to locally commited changes on that branch, give the merge some message, fix conflicts if any

STEP 3

`git stash pop` stash changes

STEP 4

`git push origin branchname -v` merged changes

Replace branchname with with master for master branch.

This normally happens when you git commit and try to git push changes before git pulling on that branch x.

Normal flow would as below,

STEP 1 : git stash your local changes on that branch

STEP 2 : git pull origin branch_name -v to pull and merge to locally commited changes on that branch, give the merge some message, fix conflicts if any

STEP 3 : git stash pop the stashed changes

STEP 4 : git push origin branch_name -v merged changes

Replace branch_name with with master (for master branch).

Source Link
prayagupadhyay
  • 30.9k
  • 14
  • 160
  • 194
Loading