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 stash temporarily saves your uncommitted changes and reverts your working directory to the last commit. It’s the escape hatch for the moment you need to switch tasks but aren’t ready to commit — a half-finished feature, a file you forgot to add, a quick bug that needs attention. Key point: A stash is a…
Cherry-picking applies a specific commit from one branch onto another. Where merge brings an entire branch and rebase replays a range of commits, cherry-pick takes one commit at a time and copies its changes to wherever you are. Key point: Cherry-pick creates a new commit with a new hash. The original stays untouched. This makes…
A tag is a permanent label on a specific commit. Unlike branches, tags don’t move — once placed, they stay on that commit forever. That makes them perfect for marking releases: v1.0, v2.3.1, v1.0.0-rc.2. When someone asks “what code was in version 1.0?”, the tag answers immediately. Key point: A tag is a named pointer…
Every repository generates files that should never be committed — build artifacts, dependency folders, editor settings, secrets. .gitignore is how Git is told to look the other way. It’s the file that keeps a repository clean, focused, and safe. Key point: .gitignore only affects untracked files. If a file is already committed, adding it to…
On a shared repository, contributors who have write access can push branches directly. But on most open-source projects, contributors don’t have that access. Forking solves this — you make your own copy of the repository, push changes there, and then ask the original project to pull them in via a pull request. Key point: A…
Good Git habits aren’t about following rules for their own sake — they’re about making history readable, reviewable, and reversible. A clean commit log tells a story. A messy one forces everyone to read diffs. This chapter covers the habits that separate a Git user from a Git practitioner. Key point: The goal of good…
The command line is the foundation of Git, but it isn’t the only way to use it. Git GUIs, IDE integrations, aliases, and hooks turn Git from a tool you type into a tool that works with you — showing history visually, catching mistakes before they happen, automating the repetitive parts. Key point: The command…
A single-page reference for the Git commands you’ll reach for most. Grouped by task, with a short description of what each does. Bookmark it — you’ll come back often. Key point: This isn’t a tutorial — it’s a lookup table. When you know what you want but not the exact syntax, find the command here….
8. Git Test Q&As a. Git Fundamentals b. Introduction to Remote Repositories c. Connecting Local to Remote d. Git Branching Questions e. Basic Branch Commands 12 .Why would you use git merge –no-ff instead of allowing fast-forward merges?You would use git merge –no-ff to force Git to create a three-way merge commit, even if a…
Git 1a Git Fundamentals Understanding Version ControlGit 1b Installing GitGit 1c Initial Git ConfigurationGit 1d The Git Workflow Local Repository Git 2a Introduction to Remote RepositoriesGit 2b Connecting Local to RemoteGit 3a Understanding BranchesGit 3b Basic Branch CommandsGit 3c Resolving Merge ConflictsGit 4a RebasingGit 4b Stashing ChangesGit 4c Cherry PickingGit 4d Tagging ReleasesGit 4e Ignoring…