Control Freak: Commit Rejected. Foxtrot Merges Not Allowed In Bitbucket
Answer : That is related to Foxtrot merges, specifcally prohibited on BitBucket: A foxtrot merge is a specific sequence of git commits. A particularly nefarious sequence. Out in the open, in lush open grasslands, the sequence looks like this: But foxtrots are rarely seen in the open. They hide up in the canopy, in-between the branches. I call them foxtrots because, when caught mid-pounce, they look like the foot sequence for the eponymous ballroom dance: Foxtrot merges are bad because they change origin/master’s first-parent history. The parents of a merge commit are ordered. The first parent is HEAD. The second parent is the commit you reference with the git merge command. You can think of it like this: git checkout 1st-parent git merge 2nd-parent If pushed: As explained in "GIT: How can I prevent foxtrot merges in my 'master' branch?", commit ' D ' is a foxtrot merge because ' origin/master ' is its 2nd parent. This is the result of a pull (fetch ...