Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
3.9.1
Description
I'm not sure if this is still persistent in newer versions of Stash/Bitbucket, but this just happened on 3.9.1:
If a user sets up a pull request, then force pushes it to be the exact same as the destination branch, Stash thinks that it was remotely merged, and marks the pull request as merged.
I understand why it thinks it's remotely merged, however the force push isn't reflected in the pull request, and it seems like the commits that are present in the PR actually made it to the destination branch, when in fact it's not actually true.
To repeat the bug:
1. Create a branch dev/test with multiple commits
2. Submit dev/test for a PR, to merge to master
3. Execute 'git reset --hard origin/master on dev/test
4. Execute 'git push origin dev/test --force'
The result will be that the PR created in step 2 will be 'Remotely Merged', yet it will not contain the action of removing commits (via the force push)
Attachments
Issue Links
- duplicates
-
BSERV-4219 Mark pull request as declined instead of merged when force push reduces mergeable commits to zero
- Closed