World map

 

BM: Baca dalam Bahasa Melayu

World 10: Deep Git

Git 3.0 preview

You will learn: what Git 3.0 plans to change, what stays the same, and how to get ready.

The problem

Git 3.0 is on its way. Will the Git you learned stop working?

Pick one answer.

Watch

Git 3.0 has no release date yet. But its plan is written down. Tap through the story.

Tap each point on the timeline.

Try it

What happens to each one in Git 3.0?

Drag a card into a box. Or tap the card, then tap the box.

        Watch

        git rev-parse HEAD prints a 40-character SHA-1 id: 9e8ddf8fb3a185e7920bc21542abe85b09f07e21. Terminal output: $ git rev-parse HEAD 9e8ddf8fb3a185e7920bc21542abe85b09f07e21

        Today’s ids are SHA-1: 40 characters. SHA-256: A stronger recipe for ids, 64 characters long. Git 3.0 plans it for new repos. ids are 64 characters long. They are much harder to fake.

        Predict

        Git 3.0 arrives. Your old repo uses SHA-1 ids. What happens to it?

        Pick one answer.

        Check

        Ready for Git 3.0? Swipe each habit.

        Swipe right for good, left for needs work. Or use the buttons.

        1 / 4

        Name your first branch main

        Name your first branch main

        You did it!

        You can now explain Git 3.0’s changes and get ready for them.

        Go deeper (optional)

        Try the future today: git init --object-format=sha256 or git init --ref-format=reftable. Check that your hosting site supports them first. safe.bareRepository becomes explicit: Git won’t use a bare repository: A repo with only the .git part and no working folder, like the copy on a server. it just stumbles into. Building Git yourself will need Rust. Source: git-scm.com/docs/BreakingChanges.