Five Ways to Break a Git Repository
summary
Five concrete ways to break a Git repo and how to fix them are demonstrated with git clone, git config, git status, checkout and commit examples. Changing core.autocrlf or missing .gitattributes turns clean clones into modified worktrees, flipping core.ignorecase or normalization flags creates untracked versus modified duplicates, disabling core.protectNTFS lets branch checkouts write into .git, and OS reserved names like aux/reserved names prevent cloning entirely (the Linux kernel won’t clone on Windows because of this).
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:00Line endings
- 3:35Core Ignore Case
- 5:54Precompose Unicode
- 8:14Protect NTFS
- 11:32Reserved File Names
related talks
13mFive Ways to Break a Git Repository
22mUsing Git in an (un)orthodox way in your team
35mThe Git you don't know
31mGit Happens or How to fix common git mistakes
39mGetting out of trouble by understanding Git
28mHow to Really Get Git
56mKnowledge is Power: Getting out of Trouble by Understanding Git
35mTerrible Ideas in Git