git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v2 13/13] pull: improve --rebase and pull.rebase interaction

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Dec 18, 2020, 21:10 UTC
Message-ID
<20201218211026.1937168-14-felipe.contreras@gmail.com>
In-Reply-To
<20201218211026.1937168-1-felipe.contreras@gmail.com>
Currently --rebase without argument overrides pull.rebase:
  git config pull.rebase merges
  git pull --rebase

Up until now this hasn't been a big issue, since user has not been forced to specify a merge, or a rebase. But with the introduction of --merge and pull.mode, the user could in theory have the following configuration:

  git config pull.mode merge
  git config pull.rebase merges
In such case, the user would expect:
  git pull --rebase
To be the same as:
  git pull --rebase=merges
If the user wants to override the configuration, she can do:
  git pull --rebase=true
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
---
 builtin/pull.c  | 10 ++++++++--
 t/t5520-pull.sh | 10 ++++++++++
 2 files changed, 18 insertions(+), 2 deletions(-)
diff --git a/builtin/pull.c b/builtin/pull.c
index ad8afabe9b..4e8e9d85a2 100644
--- a/builtin/pull.c
+++ b/builtin/pull.c
@@ -68,8 +68,14 @@ static int parse_opt_rebase(const struct option *opt, const char *arg, int unset
 
 	if (arg)
 		*value = parse_config_rebase("--rebase", arg, 0);
-	else
-		*value = unset ? REBASE_FALSE : REBASE_TRUE;
+	else {
+		if (!unset) {
+			/* --rebase shouldn't override pull.rebase=merges (and others) */
+			if (*value < REBASE_TRUE)
+				*value = REBASE_TRUE;
+		} else
+			*value = REBASE_FALSE;
+	}
 
 	if (*value > 0)
 		mode = *value >= REBASE_TRUE ? PULL_MODE_REBASE : PULL_MODE_MERGE;
diff --git a/t/t5520-pull.sh b/t/t5520-pull.sh
index 45d818065f..d0f5722eab 100755
--- a/t/t5520-pull.sh
+++ b/t/t5520-pull.sh
@@ -595,6 +595,16 @@ test_expect_success REBASE_P \
 	test_cmp_rev HEAD^2 keep-merge
 '
 
+test_expect_success REBASE_P \
+	'pull.rebase=preserve interacts correctly with pull.mode and --rebase' '
+	git reset --hard before-preserve-rebase &&
+	test_config pull.mode merge &&
+	test_config pull.rebase preserve &&
+	git pull --rebase . copy &&
+	test_cmp_rev HEAD^^ copy &&
+	test_cmp_rev HEAD^2 keep-merge
+'
+
 test_expect_success 'pull.rebase=interactive' '
 	write_script "$TRASH_DIRECTORY/fake-editor" <<-\EOF &&
 	echo I was here >fake.out &&
-- 
2.30.0.rc0
Previous: Felipe ContrerasNext: Felipe Contreras
Message 13 of 14 in “pull: pull mode part 2”
  1. 00/13 pull: pull mode part 2Felipe Contreras, Dec 18, 2020
  2. 01/13 doc: pull: explain what is a fast-forwardFelipe Contreras, Dec 18, 2020
  3. 02/13 pull: improve default warningFelipe Contreras, Dec 18, 2020
  4. 04/13 pull: trivial cleanupFelipe Contreras, Dec 18, 2020
  5. 03/13 pull: cleanup autostash checkFelipe Contreras, Dec 18, 2020
  6. 05/13 pull: trivial whitespace style fixFelipe Contreras, Dec 18, 2020
  7. 06/13 pull: introduce --merge optionFelipe Contreras, Dec 18, 2020
  8. 07/13 rebase: add REBASE_DEFAULTFelipe Contreras, Dec 18, 2020
  9. 09/13 pull: show warning with --ff optionsFelipe Contreras, Dec 18, 2020
  10. 08/13 pull: move configurations fetchesFelipe Contreras, Dec 18, 2020
  11. 10/13 pull: add pull.modeFelipe Contreras, Dec 18, 2020
  12. 12/13 pull: reorganize mode conditionalsFelipe Contreras, Dec 18, 2020
  13. 13/13 pull: improve --rebase and pull.rebase interactionFelipe Contreras, Dec 18, 2020
  14. 11/13 pull: add pull.mode=fast-forwardFelipe Contreras, Dec 18, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.