Details
-
Suggestion
-
Resolution: Fixed
Description
This is a follow up bug report from the outcome of the discussion in issue BCLOUD-13311
here is our workflow...
- git clone git@bitbucket.org:yooture/dummy.git (done by dev on local env)
- cd dummy (done by dev on local env)
- git checkout -b feature/FF (done by dev on local env)
- echo "Dany" >> contributors.txt (done by dev on local env)
- git commit -am "dany" (done by dev on local env)
- git push origin feature/FF (done by dev on local env)
- create PR for "feature/FF" via Bitbucket WebUI (check "Close feature/FF after the pull request is merged") (done by dev in browser)
- git checkout master (done by dev on local env)
- git merge feature/FF (done by dev on local env)
- git push origin master (done by dev on local env)
- git fetch origin --prune (done by dev on local env)
- git branch -r (done by dev on local env)
--> origin/feature/FF still exists
also if I do a fresh clone and list all the existing branches, feature/FF is still available...
all this is done on the origin organisation in Bitbucket (no fork is involved)
So from what was discussed with @kelwert in BCLOUD-13311, I would expect the repo "feature/FF" to be deleted after I pushed my merge commit - this seems clearly a bug on Bitbucket site then.