git push - Confused as to why Git believes my branch tip is behind the origin -


i have branch created develop (created atlassian stash) has handful of commits. when try , push commits error updates being rejected because pushed branch tip behind remote counterpart. based on understanding, means else committed, should pull changes. however, there nothing pull. funny thing looking @ atlassian stash i'm able see push has in fact gone through.

$ git push repo_url  ! [rejected]        develop -> develop (non-fast-forward)  ! [rejected]        feature/135-add-button-to-ticket-indicating -> feature/ 135-add-button-to-ticket-indicating (non-fast-forward) error: failed push refs 'repo_url' hint: updates rejected because pushed branch tip behind remote hint: counterpart. check out branch , integrate remote changes hint: (e.g. 'git pull ...') before pushing again. hint: see 'note fast-forwards' in 'git push --help' details. 

i'm not sure i'm doing wrong, love know why particular issue rears ugly head every few days. in past have have forced push, doesn't me understand why issue happening in first place.

how can diagnose why issue happening?

i faced same problem while ago, received following

git push github master git@github.com:joey-project/project.git  ! [rejected]        master -> master (non-fast-forward) error: failed push refs 'git@github.com:joey-project/project.git' 

if remember correctly, general approach use variation of following commands:

git fetch github; git merge github/master 

have tried link git push - suboptimal pack - out of memory? perhaps can further well..


Comments

Popular posts from this blog

Payment information shows nothing in one page checkout page magento -

tcpdump - How to check if server received packet (acknowledged) -