Re: Why is there no force pull?
- Date: Sat, 9 Jun 2018 13:04:30 -0700
- From: Elijah Newren <newren@xxxxxxxxx>
- Subject: Re: Why is there no force pull?
On Sat, Jun 9, 2018 at 12:01 PM, Christoph Böhmwalder
> Since this is a use case that actually comes up quite often in
> day-to-day use, especially among git beginners, I was wondering: is
> there a specific reason why a command like "fetch changes from remote,
> overwriting everything in my current working directory including all
> commits I've made" doesn't exist? Now, I'm quite aware that something
> $ git fetch origin/branch
> $ git reset --hard origin/branch
> will do the trick just fine, but (like I mentioned, especially for
> beginners) this kind of seems like a crook. Why not have a single
> command for accomplishing this? Afterall we do have a `--force` flag on
> `git push`, which practically does the same thing in reverse.
> Just reaching out to get some input on this, as it seems like a quite
> curious inconsistency to me.
Upon reading the subject and before reading the body, I assumed you
were going to ask for a 'git pull --force' that would throw away
*uncommitted* changes (i.e. do a 'git reset --hard HEAD' before the
rest of the pull). But then you asked for both uncommitted and
committed changes to be thrown away. That difference isn't something
you have to consider with a push.
That might be a reason such an option would be confusing, or it might
just be a warning to document the option carefully. Anyway, thought
I'd mention it.