All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Henrie <alexhenrie24@gmail.com>
To: git@vger.kernel.org, rcdailey.lists@gmail.com, newren@gmail.com,
	rsbecker@nexbridge.com, gitster@pobox.com, annulen@yandex.ru,
	tytso@mit.edu
Cc: Alex Henrie <alexhenrie24@gmail.com>
Subject: [PATCH v3] pull: warn if the user didn't say whether to rebase or to merge
Date: Sat, 29 Feb 2020 14:22:58 -0700	[thread overview]
Message-ID: <20200229212258.373891-1-alexhenrie24@gmail.com> (raw)

Often novice Git users forget to say "pull --rebase" and end up with an
unnecessary merge from upstream. What they usually want is either "pull
--rebase" in the simpler cases, or "pull --ff-only" to update the copy
of main integration branches, and rebase their work separately. The
pull.rebase configuration variable exists to help them in the simpler
cases, but there is no mechanism to make these users aware of it.

Issue a warning message when no --[no-]rebase option from the command
line and no pull.rebase configuration variable is given. This will
inconvenience those who never want to "pull --rebase", who haven't had
to do anything special, but the cost of the inconvenience is paid only
once per user, which should be a reasonable cost to help a number of new
users.

Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
---
v3:
- Fix segfault if opt_ff is NULL
- Don't say that the behavior will change in a future version of Git
(that hasn't been decided yet)
- Mention that pull.ff=only is also an option
- Mention git config's --global option
- Make the warning message longer and more clear in general
---
 builtin/pull.c | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/builtin/pull.c b/builtin/pull.c
index 3e624d1e00..a93ee489f6 100644
--- a/builtin/pull.c
+++ b/builtin/pull.c
@@ -327,6 +327,20 @@ static enum rebase_type config_get_rebase(void)
 	if (!git_config_get_value("pull.rebase", &value))
 		return parse_config_rebase("pull.rebase", value, 1);
 
+	if (!opt_ff || strcmp(opt_ff, "--ff-only")) {
+		warning(_("Pulling without specifying how to reconcile divergent branches\n"
+			"is discouraged. You can squelch this message by running one of the\n"
+			"following commands sometime before your next pull:\n"
+			"\n"
+			"  git config pull.rebase false  # merge (the default strategy)\n"
+			"  git config pull.rebase true   # rebase\n"
+			"  git config pull.ff only       # fast-forward only\n"
+			"\n"
+			"You can replace \"git config\" with \"git config --global\" to set a default\n"
+			"preference for all repositories. Alternatively, you can pass --rebase,\n"
+			"--no-rebase, or --ff-only on the command line every time you pull.\n"));
+	}
+
 	return REBASE_FALSE;
 }
 
-- 
2.25.1


             reply	other threads:[~2020-02-29 21:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-29 21:22 Alex Henrie [this message]
2020-02-29 23:30 ` [PATCH v3] pull: warn if the user didn't say whether to rebase or to merge Elijah Newren
2020-03-01  3:27   ` Alex Henrie
2020-03-02 21:51     ` Junio C Hamano
2020-03-02 22:37 ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200229212258.373891-1-alexhenrie24@gmail.com \
    --to=alexhenrie24@gmail.com \
    --cc=annulen@yandex.ru \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=newren@gmail.com \
    --cc=rcdailey.lists@gmail.com \
    --cc=rsbecker@nexbridge.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.