TL;DR
- Git is an incredibly powerful tool, but it can be hard to learn.
- It helps to know something about graph theory, especially with regard to reachability.
- And to know what Git's references are.
- Because references make commits reachable.
(Only got time to read one page? Make it that one.) - Once you understand that, you won't waste so much time backing up your entire repository, like I did.
- I like GitX, and you can use it (or another visualizer) to bootstrap your knowledge of Git.
- I've got a few recipes for testing out merges that give you an "undo" option.
- And I've attempted to explain rebase as simply as I can.
- About This Site
- Git Makes More Sense When You Understand X
- Example 1: Kent Beck
- Example 2: Git for Ages 4 and Up
- Example 3: Homeomorphic Endofunctors
- Example 4: LSD and Chainsaws
- The Internet Talks Back!
- Graph Theory
- Seven Bridges of Königsberg
- Places To Go, and Ways to Get There
- Nodes and Edges
- Attaching Labels to Nodes
- Attaching Labels to Edges
- Directed Versus Undirected Graphs
- Reachability
- Graphs and Git
- Visualizing Your Git Repository
- References
- The Reference Reference
- Making Sense of the Display
- Garbage Collection
- Experimenting With Git
- References Make Commits Reachable
- My Humble Beginnings
- Branches as Savepoints
- Use Your Targeting Computer, Luke
- Testing Out Merges
- Rebase From the Ground Up
- Cherry-Picking Explained
- Using 'git cherry-pick' to Simulate 'git rebase'
- A Helpful Mnemonic for 'git rebase' Arguments
- The End
