Gitflow: git-flow does not delete remote branch when published release is finished

Created on 25 May 2015 · 4Comments · Source: nvie/gitflow

git flow does not delete remote branch when a release which is published and then finished.
It deletes release branch on local but not on remote

╰─± git flow release finish v3.1.12 
Switched to branch 'master'
Merge made by the 'recursive' strategy.
 ee/cli/plugins/example.py |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Deleted branch release/v3.1.12 (was 254971c).

Summary of actions:
- Latest objects have been fetched from 'origin'
- Release branch has been merged into 'master'
- The release was tagged 'v3.1.12'
- Release branch has been back-merged into 'develop'
- Release branch 'release/v3.1.12' has been deleted

Source

harshadyeola

👍4

Most helpful comment

I had the same problem with git flow release finish 1.0.0
After pushing my tags with git push --tags
I run git push origin :release/1.0.0 and then my release remote branch was deleted on gitlab repo

rn54n on 13 Sep 2017

👍6

All 4 comments

I also have the same problem.

josejlm2 on 19 Jun 2015

Are you using the push flag (https://github.com/nvie/gitflow/blob/master/git-flow-release#L193) ? It seems that if the push flag is flipped to true, then part of the logic is to attempt to delete the remote branch (after pushing).

Reference: https://github.com/nvie/gitflow/blob/master/git-flow-release#L269-L280