{"thread":{"id":"53144","subject":"[BUG] git pull -- error: nothing to do","startedAt":"2020-03-31T16:20:24Z","lastAt":"2020-04-01T04:20:26Z","messageCount":2,"participants":["_RuRo_ (Андрей Стоцкий)","Denton Liu"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"394420","messageId":"8017591585671131@myt3-605d5ea4bc20.qloud-c.yandex.net","threadId":"53144","inReplyTo":null,"subject":"[BUG] git pull -- error: nothing to do","fromName":"_RuRo_ (Андрей Стоцкий)","fromEmail":"ruro.ruro@ya.ru","sentAt":"2020-03-31T16:15:13Z","receivedAt":"2020-03-31T16:20:24Z","isPatch":false,"sender":{"key":"ruro.ruro@ya.ru","avatar":null},"body":"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.\nWith version 2.25.1, `git pull` used to finish with exit code 0 and `Current branch master is up to date.` on stdout.\n\nThe current (`v2.26.0`) behaviour only happens with the following config options:\n```\n[pull]\n    rebase = true\n[rebase]\n    autoSquash = true\n    abbreviateCommands = true\n```\nIf any 1 of the 3 config options is not set, there is no error.\n\nI 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.\n\n-- \nAndrey Stotskiy,\nruro.ruro@ya.ru\n"},{"id":"394466","messageId":"20200401042021.GA780945@generichostname","threadId":"53144","inReplyTo":"8017591585671131@myt3-605d5ea4bc20.qloud-c.yandex.net","subject":"Re: [BUG] git pull -- error: nothing to do","fromName":"Denton Liu","fromEmail":"liu.denton@gmail.com","sentAt":"2020-04-01T04:20:21Z","receivedAt":"2020-04-01T04:20:26Z","isPatch":false,"sender":{"key":"liu.denton@gmail.com","avatar":"https://avatars.githubusercontent.com/u/9620836?v=4"},"body":"Hi Andrey,\n\nOn Tue, Mar 31, 2020 at 07:15:13PM +0300, _RuRo_ (Андрей Стоцкий) wrote:\n> 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.\n> With version 2.25.1, `git pull` used to finish with exit code 0 and `Current branch master is up to date.` on stdout.\n> \n> The current (`v2.26.0`) behaviour only happens with the following config options:\n> ```\n> [pull]\n>     rebase = true\n> [rebase]\n>     autoSquash = true\n>     abbreviateCommands = true\n> ```\n> If any 1 of the 3 config options is not set, there is no error.\n> \n> 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.\n\nI believe that this bug has been reported already. Can you see if these\npatches fix your problem:\nhttps://lore.kernel.org/git/20200330124236.6716-1-alban.gruin@gmail.com/\n\n-Denton\n\n> -- \n> Andrey Stotskiy,\n> ruro.ruro@ya.ru\n"}]}