Re: When rebase.autoStash=true is used, 'git pull' merge process still complains when incoming changes are in a different place of the file than local changes

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 23, 2022, 21:23 UTC
Message-ID: <xmqqa6ehtgz5.fsf@gitster.g>
In-Reply-To: <3101d7c2-c78c-1f96-a7c6-08979d8f246b@gmail.com>

Phillip Wood <phillip.wood123@gmail.com> writes:

Show 16 quoted lines

> On 17/02/2022 20:50, Yuri wrote:
>> I have a file "x" that has one local change and some incoming pulled
>> changes.
>> Pulled changes are contextually very far away, so it should be
>> possible to merge them without user interaction.
>> But git still complains:
>> $ git pull
>> Updating 91bfe02..522ccf2
>> error: Your local changes to the following files would be
>> overwritten by merge:
>>      x
>
> pull only uses rebase.autoStash if you ask it to rebase, if it is
> trying to merge then you need to pass --autostash on the command line
> or set merge.autoStash (assuming you want merge to always use
> --autostash).

I wonder if it would make a good #leftoverbit starter project to introduce pull.autoStash so that those who want autostash only when running "git pull" (but not "git merge" or "git rebase") can set it, ignoring the settings of merge/rebase.autoStash variables.

Thanks.