-
Bug
-
Resolution: Unresolved
-
Major
-
None
when pre build merge is enabled bitbucket approve takes incorrect hash
Merging Revision e0b1f219827408c723a81c974da67f4ed363c1aa (origin/MN-21-create-place-endpoint) to origin/develop, UserMergeOptions{mergeRemote='origin', mergeTarget='develop', mergeStrategy='default', fastForwardMode='--ff'} 19:28:00 > git rev-parse origin/develop^{commit} # timeout=10 19:28:00 > git config core.sparsecheckout # timeout=10 19:28:00 > git checkout -f origin/develop 19:28:00 > git merge --ff e0b1f219827408c723a81c974da67f4ed363c1aa # timeout=10 19:28:00 > git rev-parse HEAD^{commit} # timeout=10 19:28:00 Seen branch in repository origin/MN-21-create-place-endpoint 19:28:00 Seen branch in repository origin/develop 19:28:00 Seen branch in repository origin/master 19:28:00 Seen 3 remote branches 19:28:00 Checking out Revision 89111c1251b37a8fbb79651cbb04efc155c32f12 (origin/develop)
approve is trying to use 89111c1251b37a8fbb79651cbb04efc155c32f12 instead of e0b1f219827408c723a81c974da67f4ed363c1aa