basically, if working with more than 2 remotes, ask for strategy: original vs fork vs multi-repo
multi repo will fetch from all remotes while pushing to a specific one. on finish, it will ask to which remote to push
no remotes
treat as local (sync does nothing, everything works against the local gitflow branches)
single remote
treat as the source of truth. everything is working against a single remote repo
two remotes
treat as forked repo with an original and an owned repo if one of them is owned by the github user selected
multi repo
sync
fetch from all repos
ask where to push
finish
ask on which remote to open the pull request
no remotes is the last priority feature on this list. we should support all 3 cases and add the local option later (this is not supposed to replace the original gitflowgit plugin)
basically, if working with more than 2 remotes, ask for strategy: original vs fork vs multi-repo multi repo will fetch from all remotes while pushing to a specific one. on
finish
, it will ask to which remote to pushno remotes
treat as local (sync does nothing, everything works against the local gitflow branches)
single remote
treat as the source of truth. everything is working against a single remote repo
two remotes
treat as forked repo with an original and an owned repo if one of them is owned by the github user selected
multi repo
sync
finish
no remotes is the last priority feature on this list. we should support all 3 cases and add the local option later (this is not supposed to replace the original
gitflow
git
plugin)