From: _RuRo_ (Андрей Стоцкий) <ruro.ruro@ya.ru>
Date: Tue, 31 Mar 2020 16:15:13 GMT
Subject: [BUG] git pull -- error: nothing to do
Message-ID: <8017591585671131@myt3-605d5ea4bc20.qloud-c.yandex.net>

After updating git from `v2.25.1` to `v2.26.0`, I've noticed that performing `git pull` on an up-to-date repository now results in a non-zero exit code and `error: nothing to do` on stderr.
With version 2.25.1, `git pull` used to finish with exit code 0 and `Current branch master is up to date.` on stdout.

The current (`v2.26.0`) behaviour only happens with the following config options:
```
[pull]
    rebase = true
[rebase]
    autoSquash = true
    abbreviateCommands = true
```
If any 1 of the 3 config options is not set, there is no error.

I think, this is a bug since many scripts and utilities rely on the exit code of `git pull` and the current behaviour causes false errors.

-- 
Andrey Stotskiy,
ruro.ruro@ya.ru