Tutorials covering Git — the version control system that tracks changes, branches work, and merges contributions across teams. From the basics of commits and branches to rebasing, resolving conflicts, and the workflows that keep a repository clean. Each chapter is standalone, built around real examples and verified commands.
Git is a system that records changes to files over time, letting you recall any past version. It’s the tool every software team uses to track code, collaborate safely, and undo mistakes. This chapter covers what version control is, why Git became the industry standard, and the properties that make it different from older systems….
Git runs on every major operating system. The installation process differs by platform — Windows uses an installer with many options, Linux uses a package manager, and macOS ships Git with the developer tools. This chapter walks through each, plus verification, so you can confirm Git is ready before you start using it. 1. Installing…
Git works out of the box, but it needs a few settings before you can commit anything meaningful. The most important are your name and email — Git embeds them in every commit as the author. Beyond that, a handful of config options — editor, aliases, default branch — make daily work faster and less…
Git tracks every change to your project with fine-grained control. That control rests on one core idea: a file moves through three states — working directory, staging area, and local repository. Understanding these three states is the foundation of every Git command you’ll ever use. This chapter covers the local workflow — no remotes, no…
A remote repository is a shared, hosted copy of your Git project — the authoritative version that lives on a server instead of your machine. Your local repository holds your work; the remote holds the team’s work. Every push and pull is a conversation between the two. This chapter covers what remote repositories are, why…
A local Git repository works fine on its own — until you want to share it, back it up, or collaborate. That’s when you connect it to a remote. The link is set up once, and after that, push and pull keep the two in sync. This chapter covers the commands that establish that connection…
A branch is an independent line of development. It lets you work on a feature, a fix, or an experiment without touching the stable version of your code. In Git, branches are cheap — creating one is instant, and switching between them is fast. That’s why branching is at the center of almost every Git…
3b Basic Branch Commands Branches are Git’s working unit — you create one for each feature, fix, or experiment, then merge it back when done. The commands that manage branches are the ones you’ll type most often. This chapter covers them systematically: listing, creating, switching, merging, and deleting. Key point: Most modern Git usage replaces…
3c Resolving Merge Conflicts A merge conflict happens when Git can’t automatically combine changes from two branches. The same lines were touched in both, and Git refuses to guess which version should win. It stops the merge, marks the conflict in the affected files, and waits for you to decide. Key point: A conflict isn’t…
Rebasing rewrites commit history by replaying your branch’s commits on top of another branch. Where merge creates a merge commit and preserves both branches, rebase produces a linear history — as if you’d always been working from the latest main. Key point: Rebase rewrites history. That’s its power and its danger. It gives you a…