Git terms
Git is the version control system the entire industry converged on — and there is more to it than commit, push, and pull. This category covers branching strategies, rebasing, merging, conflict resolution, hooks, tags, and the internal object model that explains why Git behaves the way it does. Understanding Git deeply prevents disasters and enables confident collaboration.
More on Git
History
Git was created by Linus Torvalds in 2005 as a distributed version control system for Linux kernel development, replacing BitKeeper after a licensing dispute. Its design emphasized speed, distributed workflows, and data integrity through cryptographic hashing, fundamentally shifting how teams could collaborate on code without a central server dependency. Early adoption by major open-source projects and GitHub's 2008 launch as a web platform democratized Git workflows, making distributed version control the industry standard. Over the past two decades, Git practice has evolved from simple branching strategies (like Git Flow) to lighter models (GitHub Flow, trunk-based development), with tooling maturity enabling advanced workflows such as rebase-first workflows, conventional commits for automation, and CI/CD integration. Today, Git is ubiquitous across software development—from solo projects to massive monorepos—and its internal mechanisms (objects, refs, reflog) remain largely unchanged, underscoring Torvalds's original architectural insight.
Key concepts
- Git Internals
- Git Workflows Compared
- Git Rebase vs Merge
- Git Revert vs Reset vs Restore
- Git Blame & Archaeology
- Git Hooks
- Git Tags
Best references
-
Git Official Documentation The canonical reference for all Git commands, concepts, and workflows. Includes the Pro Git book (free online), man pages, and API documentation. Essential for understanding Git internals, hooks, reflog, and advanced operations.
-
GitHub Guides Practical, clearly written guides on Git workflows, collaboration, and GitHub-specific features like Actions and signed commits. Bridges the gap between Git theory and real-world team practices.
-
Conventional Commits Specification The official specification for structured commit messages. Foundation for understanding Conventional Commits Tooling and how tooling like semantic versioning and changelog generation depend on commit format standards.
-
Git Internals - Plumbing and Porcelain (Pro Git Chapter 10) Deep dive into Git's object model, refs, and low-level storage. Indispensable for understanding how bisect, reflog, rebase, and other advanced operations work under the hood.
-
Atlassian Git Tutorials Comprehensive tutorials covering workflows, rebase vs. merge strategies, cherry-pick, revert, reset, stash, and branching patterns. Well-structured for both beginners and advanced users.
-
Git Workflows Patterns and Best Practices Pro Git section on comparing integration workflows and team collaboration patterns. Contextualizes when to use rebase, merge, or cherry-pick in team settings.
Typed relationships here
Edges touching a Git term.
- Git Blame & Archaeology Alternative to Git Bisect Jun 13
- Git Workflows Compared Contains Git Rebase vs Merge Jun 10
- Git Blame & Archaeology Leverages Git Internals Jun 9
- Git Tags Applies Semantic Versioning (SemVer) Jun 9
- Git Internals Contains Git Tags Jun 7
🤖 AI Guestbook — Git educational data only
Git Revert vs Reset vs Restore
Git Workflows Compared
1.5
2
Git Bisect
1.7.14
1
Git Cherry-Pick
Git Internals
2
Git Reflog
Git Stash
1.5
1
Git Tags
3