Git development
 help / color / mirror / Atom feed
From: Vsevolod Myalitsin <ub4nal@mail.ru>
To: git@vger.kernel.org
Cc: ub4nal@mail.ru, ben.knoble@gmail.org, gitster@pobox.me, peff@peff.net
Subject: [PATCH v4 0/3] defaultBranchName advice is useless
Date: Thu, 10 Sep 2026 11:53:50 +0300	[thread overview]
Message-ID: <20260910085353.109373-1-ub4nal@mail.ru> (raw)
In-Reply-To: <20270829004959.90983-1-ub4nal@mail.ru>

The advice for setting the default branch name currently suggests
disabling it with the following command:

git config set advice.defaultBranchName false

Without an explicit scope, this command writes the setting to the
current repository's configuration. This is not particularly useful
here, since the advice is shown while initializing a repository, and
the initialization scenario does not repeat for that repository.
As a result, the setting only affects the repository where the advice
has already been shown, while the advice appears again when a new
repository is initialized.

Suggest using the global configuration scope instead, so that disabling
the advice applies to future repositories as well.

This series prepares the advice infrastructure for specifying a
configuration scope and then uses it for defaultBranchName advice.

The series is structured as follows:

1. Pass the entire advice_setting structure to vadvise().
2. Introduce a configuration scope hint for advice settings.
3. Suggest the global configuration scope for defaultBranchName advice.

Vsevolod Myalitsin (3):
  advice: pass the entire advice_setting to vadvise()
  advice: introduce advice scoping mechanism
  advice: use global config for default branch name

 advice.c | 45 ++++++++++++++++++++++++++++++++++-----------
 1 file changed, 34 insertions(+), 11 deletions(-)

-- 
2.50.1


  parent reply	other threads:[~2026-09-10  8:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2027-08-29  0:49 [PATCH v3] advice: use global config for default branch name Vsevolod Myalitsin
2026-09-09 20:27 ` Jeff King
2026-09-09 21:21   ` Junio C Hamano
2026-09-09 21:22   ` Vsevolod Myalitsin
2026-09-09 22:46     ` Jeff King
2026-09-10  4:43       ` Vsevolod Myalitsin
2026-09-09 20:50 ` Junio C Hamano
2026-09-09 21:30   ` Vsevolod Myalitsin
2026-09-09 22:31     ` Junio C Hamano
2026-09-10  8:53 ` Vsevolod Myalitsin [this message]
2026-09-10  8:53   ` [PATCH v4 1/3] advice: pass the entire advice_setting to vadvise() Vsevolod Myalitsin
2026-09-10 17:43     ` SZEDER Gábor
2026-09-10  8:53   ` [PATCH v4 2/3] advice: introduce advice scoping mechanism Vsevolod Myalitsin
2026-09-10 15:36     ` Junio C Hamano
2026-09-10 15:52       ` Jeff King
2026-09-10 17:54         ` Vsevolod Myalitsin
2026-09-10 19:05           ` Jeff King
2026-09-10 18:35         ` Junio C Hamano
2026-09-10 19:03           ` Jeff King
2026-09-10 19:54             ` Junio C Hamano
2026-09-10 20:11               ` Jeff King
2026-09-10 20:25                 ` Junio C Hamano
2026-09-12  8:12                   ` Vsevolod Myalitsin
2026-09-13 16:32                     ` Junio C Hamano
2026-09-14 17:00                       ` Jeff King
2026-09-14 19:53                         ` Junio C Hamano
2026-09-14 22:01                           ` Junio C Hamano
2026-09-17 14:03                             ` Vsevolod Myalitsin
2026-09-17 13:25                               ` Jeff King
2026-09-10  8:53   ` [PATCH v4 3/3] advice: use global config for default branch name Vsevolod Myalitsin

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=20260910085353.109373-1-ub4nal@mail.ru \
    --to=ub4nal@mail.ru \
    --cc=ben.knoble@gmail.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.me \
    --cc=peff@peff.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox