You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a specific workflow based reason that the git flow feature finish feature doesn't have a p flag like release finish to automatically push back to the target branch (such as develop) 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.
The text was updated successfully, but these errors were encountered:
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.
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.The text was updated successfully, but these errors were encountered: