How is it possible to push to origin/master but commits land in origin/some-branch? Edited


  • Team with several members
  • One member starts a branch
  • Another one makes a commit that goes to that branch
  • 3 other members are making commits (with git cmd & Idea) and pushing to master, but actually those commits are going to this branch (they don't realize about this)
  • Person who made the commit, clones a fresh copy, commits& pushes again, correctly to master.
  • Another team member commits & pushes correctly to master unadvertently. His previous commits had gone to the branch.
  • At some point we realize of this. Checking local working copies, commits are in master & origin/master, checking bitbucket page they are on this other branch
  • Fetching we get actual remote status in our local with no issues
  • One of us cherry picked all the commits that should be on master to master, pushed them and every thing went alright

How is this possible in general? What's the mecanism that allows this behavior? 

For some time working copies were pushing to their origin/master, although commits were landing in origin/some-branch.

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 14, 2019 in Bitbucket Pipelines

Building a Bitbucket Pipe as a casual coder :  #!/bin/bash source "$(dirname "$0")/" enable_debug extra_args="" if [[ "${DEBUG}" == "true" ]]; then extra_args="--verbose" fi # mandatory variables R...

274 views 0 12
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you