GitHub
The version control layer every engineering team runs on — built on git's immutable object model, extended with collaboration, CI/CD, and project tooling.
setup & config
commits & objects
branching
rebase vs merge
pull requests
remote workflow
GitHub Actions
collaboration patterns
Topic overview
Git's content-addressable object model, the three working areas, branching and merge strategies, remote workflow mechanics, rebase vs merge trade-offs, pull request review patterns, team collaboration workflows, and CI/CD automation with GitHub Actions.
Core concepts
Blob, tree, commit objects, DAG, HEAD, staging area, fast-forward vs three-way merge, fetch vs pull, rebase golden rule, interactive rebase, squash merge, branch protection, trunk-based development, GitFlow, workflow YAML, triggers, jobs, and steps.
Why it matters
Git is the one tool every engineer uses daily regardless of role. Knowing the object model rather than just the commands means you never get stuck — you can reconstruct lost work, clean up any history mess, and explain your choices confidently. Misusing rebase on shared branches or not understanding merge strategies causes team-wide problems.
Interview relevance
Merge vs rebase, the three-areas model, and how to recover from common mistakes reveal whether you use git mechanically or truly understand it. Collaboration workflow choices reveal real team experience.