summaryrefslogtreecommitdiff
path: root/t/unit-tests/u-urlmatch-normalization.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2025-09-17 09:18:28 -0700
committerJunio C Hamano <gitster@pobox.com>2025-09-18 11:44:47 -0700
commit373ad8917beb99dc643b6e7f5c117a294384a57e (patch)
treec5fe4069b591394d9fd078b7037a8c32c8b326d7 /t/unit-tests/u-urlmatch-normalization.c
parent5590b4e7f52017794169a93d571204141bab3d28 (diff)
initial branch: give hints after switching the default name
It is likely that those who came to Git after 3.0 switched the default initial branch name to 'main' would still try to follow tutorials that were written before 3.0 happened and with the assumption that the tool would call the initial branch 'master'. To help these new users after 3.0 boundary, let's retain one part of the hint we will be giving before the default changes, namely, how to rename the branch an unconfigured Git has created just once. We do this without telling them how to permanently configure the default name of the initial branch, and that design choice is very much deliberate. The whole point of switching the default name was because we did not want to force individual users to configure their default branch name but while the hard wired default was 'master', they _had_ to configure it away from 'master' in order to conform to the recent norm, and a hint that tells them how to do so is useful. But once the default is renamed to 'main', that no longer is true. A narrower audience who are new users that follow an instruction that assumes the initial branch name is 'master' would only need to learn "here is how to change the branch name to match the tutorial you are following in the repository you created for practice", and "here is how you keep creating repositories with the first branch with a name everybody hates" is unnecessary. It also needs to be noted that the advise token to squelch the message is the same advice.defaultBranchName as before, which is also very much deliberate. The users who do have that configured are those who _have_ been using Git since before 3.0, and they are not the target audience for the new advice message. Reusing the same advise token ensures that they do not have to turn the message off. Helped-by: Phillip Wood <phillip.wood@dunelm.org.uk> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/unit-tests/u-urlmatch-normalization.c')
0 files changed, 0 insertions, 0 deletions