Git Quicke Commands Guide

Inside the book

This preview is derived from headings detected in the PDF’s opening pages.

• Git Quick Commands Guide Prepared by Ayman Alheraki forgevm.org December 2025 Git as an Engineering System Git is not merely a tool for saving code snapshots. It is a distributed system for tracking intent, change, ownership, and historical decisions across time and teams. This chapter presents Git commands as structured operations on a well-defined internal model: the working tree, the index (staging area), and the object database. The Git Mental Model Git operates on three primary layers: • Working Directory — your editable files • Staging Area (Index) — selected changes prepared for commit • Repository (Object Database) — immutable history Understanding these layers is mandatory before using Git professionally. Repository Initialization and Identity Initializing a Repository git init 2 3 Creates a new repository by initializing the .git directory. No files are tracked until explicitly added. Cloning an Existing Repository git clone https://example.com/project.git Cloning copies: • full commit history • branches • tags • remote references Configuring Identity git config --global user.name "Ayman Alheraki" git config --global user.email "ayman@example.com" Identity is embedded into every commit object and should never be skipped. Working Directory Discipline Inspecting Repository State git status Shows: • untracked files 4 • modified files • staged files This command should be executed frequently. Adding Files to the Index git add file.cpp git add src/ git add . Staging is a selection process, not a formality. Partial Staging git add -p Allows staging changes hunk-by-hunk.