Every professional software team relies on version control, and Git is the industry standard — this deck of 20 flashcards covers everything you need to collaborate confidently on code. You'll learn what a repository is and the core commands for everyday work:...
Every professional software team relies on version control, and Git is the industry standard — this deck of 20 flashcards covers everything you need to collaborate confidently on code. You'll learn what a repository is and the core commands for everyday work: init, clone, add, commit, push and pull, then move into branching and merging, including how to resolve merge conflicts when they occur. The deck also explains pull requests and code review workflows, the purpose of a .gitignore file, and the difference between git revert and git reset, finishing with forking versus cloning and how commit hashes work. Useful for anyone starting a software development course, joining a development team, or preparing for a technical interview, this deck builds the practical vocabulary and command knowledge needed to work in a real Git-based workflow from day one.
Ready to test yourself?
Flip through all 20 cards in interactive study mode.
A system that tracks and manages changes to files over time, allowing multiple people to collaborate and revert to previous versions when needed.
A distributed version control system that tracks changes in source code, allowing multiple developers to work on a project independently and merge changes.
A storage location containing a project's files along with the complete history of changes made to them, tracked by Git.
Initialises a new, empty Git repository in the current directory.
Creates a local copy of a remote repository, including its full history.
Stages changes (moves them to the "staging area"), preparing them to be included in the next commit.
Saves the currently staged changes as a permanent snapshot in the repository's history, with a descriptive message.
Uploads local commits to a remote repository (such as GitHub), sharing changes with collaborators.
Fetches changes from a remote repository and merges them into the current local branch.
An independent line of development, allowing work on new features or fixes without affecting the main codebase until merged.
git branch creates a new branch. git checkout switches to it (or git checkout -b does both at once).
Combines the changes from one branch into another, typically merging a feature branch back into the main branch.
An error that occurs when Git cannot automatically reconcile changes made to the same part of a file in two different branches, requiring manual resolution.
A request to merge changes from one branch (or fork) into another, typically used on platforms like GitHub to enable code review before merging.
The current state of the working directory and staging area, showing which files are modified, staged, or untracked.
The commit history of the current branch, including commit hashes, authors, dates and messages.
Specifying files and directories that Git should not track (e.g. build artifacts, environment files, dependencies).
git revert creates a new commit that undoes previous changes, preserving history. git reset moves the branch pointer backward, potentially discarding commits/history.
A fork creates your own independent copy of someone else's repository on the hosting platform (e.g. GitHub), typically to contribute changes back via pull request. A clone just downloads a local copy.
A unique identifier (a SHA-1 checksum) automatically assigned to each commit, used to reference specific points in a repository's history.
