Git

A working engineer’s playbook for going from first commit to GitHub Actions, code review, security, and Codespaces — without the usual tutorial fluff.

Table of Contents Introduction What Are Git Submodules? When to Use Submodules vs. Alternatives Setting Up a Submodule 4.1 Adding a Submodule 4.2 Cloning a Repository with Submodules 4.3 Updating Submodules Common Workflows 5.1 Making Changes Inside a Submodule 5.2 Propagating Changes to the Parent Repo 5.3 Branching Strategies Managing Submodule Versions 6.1 Pinning Specific Commits 6.2 Using Tags and Branches Nested Submodules Best Practices 8.1 The .gitmodules File 8.2 .gitignore Considerations 8.3 CI/CD Integration 8.4 Automation Scripts Common Pitfalls and How to Avoid Them 9.1 Detached HEAD Syndrome 9.2 Merge Conflicts Across Submodules 9.3 Removing a Submodule Cleanly Migrating Away from Submodules Advanced Topics 11.1 SSH vs. HTTPS URLs 11.2 Changing Submodule Paths 11.3 git submodule update --remote Real‑World Use Cases 12.1 Vendor Libraries 12.2 Micro‑service Repositories FAQ 14Conclusion 15Resources Introduction Git is the de‑facto standard for distributed version control, and its flexibility lets teams model almost any code‑organization strategy. One of the more nuanced features is Git submodules, a mechanism that lets one repository (the super‑project) embed another Git repository at a specific directory path. Submodules have been around since Git 1.5, but they remain a source of confusion, frustration, and, when used correctly, powerful modularity. ...

Introduction Git has become the de‑facto standard for source‑code version control, and with its rise comes a growing demand for flexible workflows. While most developers are comfortable with the classic clone‑and‑checkout model, larger teams, CI pipelines, and multi‑project monorepos often require something more sophisticated. Enter git worktree, a powerful command that lets you have multiple working directories attached to a single repository. But a worktree is not just a convenience; it can be a source of subtle bugs if the directories interfere with each other. Worktree isolation—the practice of keeping each worktree completely independent from the rest—ensures that changes, builds, and tests in one environment never bleed into another. This article provides a comprehensive, in‑depth guide to mastering worktree isolation, from fundamentals to advanced techniques, bolstered by real‑world examples and best‑practice recommendations. ...

Introduction Git has become the de‑facto standard for source‑code management, powering everything from tiny hobby projects to the world’s largest open‑source ecosystems. Its reputation for speed, integrity, and flexibility stems from a set of elegant, low‑level design decisions that were deliberately kept simple enough to be re‑implemented by a single developer in a weekend. If you’ve ever wondered how Git works under the hood, building a tiny clone is the most effective way to find out. In this article we’ll walk through the core concepts that make Git possible, then construct a minimal, functional Git‑like system in Python. The goal isn’t to replace the official implementation, but to expose the plumbing that powers the high‑level commands you use daily. ...

Introduction Git has become the de‑facto standard for source‑code version control, and most developers are comfortable with the classic workflow of git clone, git checkout, and git merge. Yet, as projects grow in size and complexity, the traditional model can start to feel limiting. Imagine needing to work on several long‑running feature branches simultaneously, or needing a clean checkout of a previous release for a hot‑fix while your main development environment stays on the latest main branch. ...