You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"GitHub changed the default branch name from master to main in mid-2020, and other Git hosts followed suit.
So you may find that the default branch name in some newly created repositories is main and not master.
In addition, the default branch name can be changed (as you have seen in <<ch01-getting-started#_new_default_branch>>), so you may see a different name for the default branch.
However, Git itself still uses master as the default, so we will use it throughout the book_."
But git don't use master as a default anymore so it really should be the other way round - using the term mainthroughout the book and have a note informing that prior to XX date masterwas the default branch and that's why you may see it many projects.
I'm beginning to realize I might (unknowingly) be poking in an open wound here.
What problem will this solve?
It would remove the term mastermaking it more coherent with the terminology now used.
Have you thought about other solutions?
No response
Do you want to help with this enhancement idea?
Yes! But I need some assistance and verification that this is a change you'll want to merge.
The text was updated successfully, but these errors were encountered:
General overview of your idea.
This note was merged in February 2022:
"GitHub changed the default branch name from
master
tomain
in mid-2020, and other Git hosts followed suit.So you may find that the default branch name in some newly created repositories is
main
and notmaster
.In addition, the default branch name can be changed (as you have seen in <<ch01-getting-started#_new_default_branch>>), so you may see a different name for the default branch.
However, Git itself still uses
master
as the default, so we will use it throughout the book_."But git don't use
master
as a default anymore so it really should be the other way round - using the termmain
throughout the book and have a note informing that prior to XX datemaster
was the default branch and that's why you may see it many projects.I'm beginning to realize I might (unknowingly) be poking in an open wound here.
What problem will this solve?
It would remove the term
master
making it more coherent with the terminology now used.Have you thought about other solutions?
No response
Do you want to help with this enhancement idea?
Yes! But I need some assistance and verification that this is a change you'll want to merge.
The text was updated successfully, but these errors were encountered: