18/11/2026 00:00am

Git 3.0 Is Coming: main as Default Branch, SHA-256 and reftable. What Git Learners Should Check
#Git
#Git 3.0
#SHA-256
#default branch
#reftable
Ever wondered why a brand-new repository starts with a different branch name on different machines? Some get master, some get main, even though everyone runs the same git init. Part of it comes from each person's local settings, and part of it comes from a plan the Git team has written down: one day the default will be set to match everywhere.
That plan lives in a document called Breaking Changes, which collects what will change in Git 3.0. Today Superdev Academy walks through what the document says, what people learning Git should know, and what you can check on your own machine starting today.
What is Git 3.0, and when will it ship?
Git 3.0 is the next major release, which the Git developers have set aside as the place to gather changes that may make existing behavior work differently (breaking changes). According to the BreakingChanges document on git-scm, there is no release date for this version yet.
We read the document on 12 November 2026, and its content is a plan that the Git team can still edit. Anything written as "will change" is best read as a direction, not a promise.
What the document plans
The document lists five main items, and the top three are stated to apply to newly created repositories.
Hash function: the default for new repos changes from SHA-1 to SHA-256. The document adds that there is no plan to drop support for the SHA-1 format.
Reference storage (such as branch and tag names): the default for new repos changes from the
filesformat toreftable.The default branch name in new repos will be
main.Building Git will require Rust. The document also says the team may postpone this to a later minor release if it affects downstream distributions too much.
The
safe.bareRepositorysetting changes fromalltoexplicit. If you want the old behavior, setsafe.bareRepository=allin your personal or system configuration.
There are also items slated for removal, such as the grafts mechanism, the git-pack-redundant and git-whatchanged commands, --stdin support in name-rev, remote shorthand stored in the branches/ and remotes/ folders, and the settings core.commentString=auto and core.preferSymlinkRefs=true.
What it means if you are just learning Git
The good news for beginners is that most of the changes touch newly created repos, and everyday commands like add, commit and push are not on the document's removal list. Still, three things affect your basic understanding.
First, the branch name. If the textbook or video you are learning from talks about master, know that the coming default is main, which already matches what GitHub uses for many new repos. Second, commit hashes will be longer if a new repo uses SHA-256. Third, if you have ever opened the .git/refs folder to see where branches are stored, the reftable format stores them differently.
Check your own machine today
Our team ran the commands below on Git 2.50.1 in a temporary folder, and the results came out as described. Your machine may differ depending on your version and settings.
1. Check the version and the default branch name
git --version
git config --global --get init.defaultBranchIf the second line prints nothing, you have not set this value. If you want your new repos to always start with main, set it with git config --global init.defaultBranch main.
2. Try creating a SHA-256 repo
mkdir try-sha256 && cd try-sha256
git init --object-format=sha256
git rev-parse --show-object-format
git commit --allow-empty -m "try sha256"
git log --format=%HOn the machine we tested, git rev-parse --show-object-format printed sha256 and the commit hash was 64 characters long, while a regular repo printed sha1. Do this in a scratch folder and delete it afterwards. We have not checked how well GitHub or the tools your team uses support this kind of repo, so we do not recommend moving real work to it yet.
3. Try the safe.bareRepository setting
git -c safe.bareRepository=explicit config --get safe.bareRepositoryThis uses a temporary value for this one command and prints explicit back. It does not edit your configuration files.
No release date yet: should you care now?
There is no need to rush. The document has no date, and the first three items concern new repos. Doing nothing today will not break your existing repos tomorrow.
Two cheap things are still worth doing. One is to set init.defaultBranch to the name you want. The other is that if you have a script or CI that assumes hashes are 40 characters long, or that the branch must be named master, write it down as a place to recheck once Git 3.0 has a real release date. We cover team branch naming rules separately in GitHub Workflow 2026.
Summary: read the direction, then pick up the small things you can do today
According to the Breaking Changes document, Git 3.0 plans to make SHA-256, reftable and a branch named main the defaults for new repos, require Rust to build, and change safe.bareRepository to explicit, with no release date yet.
What you can do in a few minutes is run git --version, set init.defaultBranch, and try creating a SHA-256 repo in a scratch folder once. When you see a 64-character hash with your own eyes, you will understand what the document is talking about far better than by reading alone.
If you want to get fluent with branches, Pull Requests and code review, take a look at the Git & GitHub Essentials course from Superdev Academy. It runs 2 hours across 42 lessons, is taught in Thai, and comes with course materials and a certificate, with 12 months of access. It covers everyday Git and GitHub fundamentals, not Git 3.0 specifically. Browse all courses at learn.superdevacademy.com/courses.
🎯 Follow dev knowledge from Superdev Academy:
🔵 Facebook: Superdev Academy Thailand
🎬 YouTube: Superdev Academy Channel
📸 Instagram: @superdevacademy
🎬 TikTok: @superdevacademy
FAQ: Frequently Asked Questions about This Article
A collection of questions and answers to help you better understand the content of this article.