-
Notifications
You must be signed in to change notification settings - Fork 528
git feature pull/track/checkout confusing #128
Comments
Yeah that one's a major head scratcher :) In the gitflow plugin I'm developing for intelliJ I've even removed |
Yes, would be great to remove |
It is all confusing. Lets figure out how to improve and stay as close to original git commands as possible. Current situation in git-flowPull
Track
Checkout
My thoughtsCheckout
Track
Pull
Let me know your thoughts on this. |
IMO, If |
Why not combine |
Why? Do you want to replace |
For windows users without bash and autocomplete, |
just want to confirm that "git flow feature checkout {feature_name}" will be removed and resort to use normal "git checkout {feature_name}" instead? |
I'm a bit confused about what to use to replace I start tracking a feature on my remote with A couple days later, I want to work on that feature, but before that I want to pull any changes other might have made to it from remote What should i use instead of This kind of scenario is quite common indeed, I feel like the documentation is a bit lacking about it |
@opensas you can just check out the branch |
While the solution works using plain git command, in my workflow, I mostly use git flow commands, this was inherited from usage from the IDE/editor that handles the add/commit phase, and then I choose to pull/push remotes using git flow commands or sometimes another plugin for gitflow either. |
The information available about what git feature pull/track/checkout is lacking. I find it very confusing and don't know what the difference is.
pull doesn't seem to track, according to this:
http://stackoverflow.com/questions/18412750/why-doesnt-git-flow-feature-pull-track
The documentation here, or in the commandline, doesn't explain the difference:
https://github.com/petervanderdoes/gitflow/wiki/Reference:-git-flow-feature
The text was updated successfully, but these errors were encountered: