Open davidgoate opened 6 years ago
Seconded.
This strikes me as the worst of both worlds: the commands cannot be relied upon to be 'local only', but neither can they be relied upon to be fully transactional and avoid unexpected states in the remote repo.
Update: The feature has been implemented as git flow feature finish --push
(you cannot use -p
), here.
(Remember that this nvie/gitflow
repo is the deprecated old repo that we should no longer use!)
Is there a specific workflow based reason that the
git flow feature finish
feature doesn't have ap
flag like release finish to automatically push back to the target branch (such asdevelop
) after?Admittedly I can create some alias which automatically does the feature finish then does a
git push origin develop
after so something similar, but I was curious from an educational perspective why release finish warranted it but feature finish did not.