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

[PATCH v4 07/19] pull: display default warning only when non-ff

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Dec 8, 2020, 00:26 UTC
Message-ID
<20201208002648.1370414-8-felipe.contreras@gmail.com>
In-Reply-To
<20201208002648.1370414-1-felipe.contreras@gmail.com>

There's no need to display the annoying warning on every pull... only the ones that are not fast-forward.

This requires the tests to pick another base, so the merge is not fast-forward. And in the cases where --ff-only is specified add test_must_fail (since now they are non-fast-forward).

Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
---
 Documentation/git-pull.txt   |  3 +++
 builtin/pull.c               |  2 +-
 t/t7601-merge-pull-config.sh | 28 +++++++++++++++++-----------
 3 files changed, 21 insertions(+), 12 deletions(-)
diff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt
index e1605a81b3..2fb184ab5f 100644
--- a/Documentation/git-pull.txt
+++ b/Documentation/git-pull.txt
@@ -60,6 +60,9 @@ However, a non-fast-forward case looks very different.
 	origin/master in your repository
 ------------
 
+By default `git pull` will warn about these situations, however, most likely
+you would want to force a merge, which you can do with `git pull --no-rebase`.
+
 Then "`git pull`" will fetch and replay the changes from the remote
 `master` branch since it diverged from the local `master` (i.e., `E`)
 until its current commit (`C`) on top of `master` and record the
diff --git a/builtin/pull.c b/builtin/pull.c
index 3b84ebf100..ab410d675f 100644
--- a/builtin/pull.c
+++ b/builtin/pull.c
@@ -1031,7 +1031,7 @@ int cmd_pull(int argc, const char **argv, const char *prefix)
 
 	can_ff = get_can_ff(&orig_head, &merge_heads.oid[0]);
 
-	if (default_mode && opt_verbosity >= 0 && !opt_ff) {
+	if (default_mode && !can_ff && opt_verbosity >= 0 && !opt_ff) {
 		advise(_("Pulling without specifying how to reconcile divergent branches is discouraged;\n"
 			"you need to specify if you want a merge, or a rebase.\n"
 			"You can squelch this message by running one of the following commands:\n"
diff --git a/t/t7601-merge-pull-config.sh b/t/t7601-merge-pull-config.sh
index 6774e9d86f..6b4adab8b1 100755
--- a/t/t7601-merge-pull-config.sh
+++ b/t/t7601-merge-pull-config.sh
@@ -28,7 +28,7 @@ test_expect_success 'setup' '
 '
 
 test_expect_success 'pull.rebase not set' '
-	git reset --hard c0 &&
+	git reset --hard c2 &&
 	git -c color.advice=always pull . c1 2>err &&
 	test_decode_color <err >decoded &&
 	test_i18ngrep "<YELLOW>hint: " decoded &&
@@ -36,54 +36,60 @@ test_expect_success 'pull.rebase not set' '
 
 '
 
-test_expect_success 'pull.rebase not set and pull.ff=true' '
+test_expect_success 'pull.rebase not set (fast-forward)' '
 	git reset --hard c0 &&
+	git pull . c1 2>err &&
+	test_i18ngrep ! "Pulling without specifying how to reconcile" err
+'
+
+test_expect_success 'pull.rebase not set and pull.ff=true' '
+	git reset --hard c2 &&
 	test_config pull.ff true &&
 	git pull . c1 2>err &&
 	test_i18ngrep ! "Pulling without specifying how to reconcile" err
 '
 
 test_expect_success 'pull.rebase not set and pull.ff=false' '
-	git reset --hard c0 &&
+	git reset --hard c2 &&
 	test_config pull.ff false &&
 	git pull . c1 2>err &&
 	test_i18ngrep ! "Pulling without specifying how to reconcile" err
 '
 
 test_expect_success 'pull.rebase not set and pull.ff=only' '
-	git reset --hard c0 &&
+	git reset --hard c2 &&
 	test_config pull.ff only &&
-	git pull . c1 2>err &&
+	test_must_fail git pull . c1 2>err &&
 	test_i18ngrep ! "Pulling without specifying how to reconcile" err
 '
 
 test_expect_success 'pull.rebase not set and --rebase given' '
-	git reset --hard c0 &&
+	git reset --hard c2 &&
 	git pull --rebase . c1 2>err &&
 	test_i18ngrep ! "Pulling without specifying how to reconcile" err
 '
 
 test_expect_success 'pull.rebase not set and --no-rebase given' '
-	git reset --hard c0 &&
+	git reset --hard c2 &&
 	git pull --no-rebase . c1 2>err &&
 	test_i18ngrep ! "Pulling without specifying how to reconcile" err
 '
 
 test_expect_success 'pull.rebase not set and --ff given' '
-	git reset --hard c0 &&
+	git reset --hard c2 &&
 	git pull --ff . c1 2>err &&
 	test_i18ngrep ! "Pulling without specifying how to reconcile" err
 '
 
 test_expect_success 'pull.rebase not set and --no-ff given' '
-	git reset --hard c0 &&
+	git reset --hard c2 &&
 	git pull --no-ff . c1 2>err &&
 	test_i18ngrep ! "Pulling without specifying how to reconcile" err
 '
 
 test_expect_success 'pull.rebase not set and --ff-only given' '
-	git reset --hard c0 &&
-	git pull --ff-only . c1 2>err &&
+	git reset --hard c2 &&
+	test_must_fail git pull --ff-only . c1 2>err &&
 	test_i18ngrep ! "Pulling without specifying how to reconcile" err
 '
 
-- 
2.29.2
Previous: Felipe ContrerasNext: Felipe Contreras
Message 8 of 21 in “pull: default ff-only mode”
  1. 00/19 pull: default ff-only modeFelipe Contreras, Dec 8, 2020
  2. 01/19 doc: pull: explain what is a fast-forwardFelipe Contreras, Dec 8, 2020
  3. 02/19 pull: improve default warningFelipe Contreras, Dec 8, 2020
  4. 03/19 pull: refactor fast-forward checkFelipe Contreras, Dec 8, 2020
  5. 04/19 pull: cleanup autostash checkFelipe Contreras, Dec 8, 2020
  6. 06/19 pull: move default warningFelipe Contreras, Dec 8, 2020
  7. 05/19 pull: trivial cleanupFelipe Contreras, Dec 8, 2020
  8. 07/19 pull: display default warning only when non-ffFelipe Contreras, Dec 8, 2020
  9. 08/19 pull: trivial whitespace style fixFelipe Contreras, Dec 8, 2020
  10. 09/19 pull: introduce --merge optionFelipe Contreras, Dec 8, 2020
  11. 10/19 pull: show warning with --ffFelipe Contreras, Dec 8, 2020
  12. 11/19 rebase: add REBASE_DEFAULTFelipe Contreras, Dec 8, 2020
  13. 12/19 pull: move configurations fetchesFelipe Contreras, Dec 8, 2020
  14. 14/19 test: pull-options: revert unnecessary changesFelipe Contreras, Dec 8, 2020
  15. 15/19 pull: trivial memory fixFelipe Contreras, Dec 8, 2020
  16. 13/19 test: merge-pull-config: trivial cleanupFelipe Contreras, Dec 8, 2020
  17. 17/19 pull: add pull.mode=ff-onlyFelipe Contreras, Dec 8, 2020
  18. 19/19 future: pull: enable ff-only mode by defaultFelipe Contreras, Dec 8, 2020
  19. 16/19 pull: add pull.modeFelipe Contreras, Dec 8, 2020
  20. 18/19 pull: advice of future changesFelipe Contreras, Dec 8, 2020
  21. Felipe ContrerasDec 8, 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.