# Git flash cards: Master level

63 Git terms at the Master level, as flash cards.

Updated: November 17, 2026

- [Study these as flash cards](https://www.ask-codey.com/decks/git/5/flash)
- [Play Memory with them](https://www.ask-codey.com/games/memory?category=git&level=5)

## Terms in this deck

- [Alternate object database](https://www.ask-codey.com/glossary/alternate-object-database): Another object directory a repository is configured to search for objects it does not store itself.
- [Background maintenance](https://www.ask-codey.com/glossary/background-maintenance): Scheduled or incremental repository tasks that improve performance without a full manual cleanup.
- [Blob object](https://www.ask-codey.com/glossary/blob-object): A Git object that stores file content without the file's name or path.
- [Cache tree](https://www.ask-codey.com/glossary/cache-tree): Index extension data that caches tree object information for directories whose entries have not changed.
- [Capability advertisement](https://www.ask-codey.com/glossary/capability-advertisement): The protocol exchange that tells the other side which optional Git features are supported.
- [Commit object](https://www.ask-codey.com/glossary/commit-object): A Git object that identifies a root tree, parent commits, author data, committer data, and a message.
- [Commit-graph file](https://www.ask-codey.com/glossary/commit-graph-file): A derived file that stores commit relationships and generation data to speed history queries.
- [Content-addressable storage](https://www.ask-codey.com/glossary/content-addressable-storage): Storage ID used by git that is based on what is in the file.
- [Cruft pack](https://www.ask-codey.com/glossary/cruft-pack): A packfile that stores unreachable objects together with information about when they became eligible for expiry.
- [Dangling object](https://www.ask-codey.com/glossary/dangling-object): An unreachable object that is not used by another unreachable object.
- [Delta chain](https://www.ask-codey.com/glossary/delta-chain): A sequence of delta-compressed objects that must be combined to reconstruct an object.
- [Delta compression](https://www.ask-codey.com/glossary/delta-compression): Storing one object's differences from another object to reduce packfile size.
- [Dumb protocol](https://www.ask-codey.com/glossary/dumb-protocol): A basic transfer method that serves repository files without Git-aware negotiation on the server.
- [Fetch negotiation](https://www.ask-codey.com/glossary/fetch-negotiation): The part of a fetch where client and server identify common history and decide what objects are needed.
- [File system monitor](https://www.ask-codey.com/glossary/file-system-monitor): A service that tells Git which working-tree paths may have changed since an earlier check.
- [Garbage collection](https://www.ask-codey.com/glossary/garbage-collection-git): Repository maintenance that consolidates storage and eventually removes expired unreachable data.
- [Generation number](https://www.ask-codey.com/glossary/generation-number): A commit-graph value that helps Git avoid walking into history that cannot contain a desired commit.
- [git cat-file](https://www.ask-codey.com/glossary/git-cat-file): Displays object types, sizes, or contents directly from the object database.
- [git commit-tree](https://www.ask-codey.com/glossary/git-commit-tree): Creates a commit object from a tree, message, parent information, and identity environment.
- [git fsck](https://www.ask-codey.com/glossary/git-fsck): Checks object connectivity and validity and reports unreachable or damaged objects.
- [git gc](https://www.ask-codey.com/glossary/git-gc): Runs repository housekeeping such as packing objects, cleaning auxiliary data, and pruning eligible objects.
- [git hash-object](https://www.ask-codey.com/glossary/git-hash-object): Calculates an object ID for content and can optionally write the resulting blob object.
- [Git object model](https://www.ask-codey.com/glossary/git-object-model): The system in which blobs, trees, commits, and annotated tags form Git's stored history.
- [Git protocol](https://www.ask-codey.com/glossary/git-protocol): The rules Git clients and servers use to advertise references and transfer repository data.
- [git prune](https://www.ask-codey.com/glossary/git-prune): Deletes unreachable loose objects that are older than the selected expiration time.
- [git write-tree](https://www.ask-codey.com/glossary/git-write-tree): Creates a tree object from the current index and prints its object ID.
- [Index entry](https://www.ask-codey.com/glossary/index-entry): The index record for one tracked path, including its object ID, mode, stage, and cached file information.
- [Index stage](https://www.ask-codey.com/glossary/index-stage): A number identifying the normal entry or one side of an unresolved merge in the index.
- [Loose object](https://www.ask-codey.com/glossary/loose-object): An individual Git object stored in its own compressed file.
- [Merge strategy](https://www.ask-codey.com/glossary/merge-strategy): The high-level algorithm Git uses to combine commit histories.
- [Multi-pack-index](https://www.ask-codey.com/glossary/multi-pack-index): An index that locates objects across multiple packfiles without combining those packs.
- [Object corruption](https://www.ask-codey.com/glossary/object-corruption): Damage or inconsistency that prevents a stored Git object from matching or decoding under its object ID.
- [Object database](https://www.ask-codey.com/glossary/object-database): The repository storage that holds Git objects addressed by their object IDs.
- [Object header](https://www.ask-codey.com/glossary/object-header): The object type and content length included when Git calculates an object's ID.
- [Object negotiation](https://www.ask-codey.com/glossary/object-negotiation): The exchange used to determine which objects one repository must send to another.
- [Object pruning](https://www.ask-codey.com/glossary/object-pruning): Permanently deleting eligible unreachable objects from the object database.
- [Octopus merge](https://www.ask-codey.com/glossary/octopus-merge): A merge that combines more than two other branch tips in one merge commit.
- [Ort strategy](https://www.ask-codey.com/glossary/ort-strategy): Git's default strategy for typical two-head merges, designed for correctness and performance.
- [Pack index](https://www.ask-codey.com/glossary/pack-index): A companion file that helps Git quickly locate objects inside a packfile.
- [Packed object](https://www.ask-codey.com/glossary/packed-object): A Git object stored inside a packfile, possibly as a delta from another object.
- [Packed refs](https://www.ask-codey.com/glossary/packed-refs): A file that stores many references together instead of as separate loose reference files.
- [Packet line](https://www.ask-codey.com/glossary/packet-line): A length-prefixed message unit used by Git's wire protocols.
- [Packfile](https://www.ask-codey.com/glossary/packfile): A file that stores many compressed Git objects together.
- [Protocol version 2](https://www.ask-codey.com/glossary/protocol-version-2): A Git wire-protocol version that requests capabilities and commands in a more structured, extensible exchange.
- [Quarantine environment](https://www.ask-codey.com/glossary/quarantine-environment): Temporary object storage used to inspect received objects before accepting them into a repository.
- [Reachability bitmap](https://www.ask-codey.com/glossary/reachability-bitmap): A compact record of object reachability used to accelerate traversals and object negotiation.
- [Reachable object](https://www.ask-codey.com/glossary/reachable-object): An object that can be found by following links from a selected reference or other starting point.
- [Recursive merge](https://www.ask-codey.com/glossary/recursive-merge): The former default two-head merge strategy that can combine multiple merge bases recursively.
- [Reference transaction](https://www.ask-codey.com/glossary/reference-transaction): A group of reference updates prepared and committed together under Git's reference rules.
- [Reflog expiration](https://www.ask-codey.com/glossary/reflog-expiration): The process of removing reflog entries after configured retention periods.
- [Repository integrity](https://www.ask-codey.com/glossary/repository-integrity): The condition in which repository objects and references are valid, connected as expected, and uncorrupted.
- [Shallow boundary](https://www.ask-codey.com/glossary/shallow-boundary): A recorded commit treated as having no parents because earlier history is absent from a shallow repository.
- [Sideband](https://www.ask-codey.com/glossary/sideband): A protocol channel that multiplexes pack data, progress messages, and errors over one connection.
- [Smart protocol](https://www.ask-codey.com/glossary/smart-protocol): A Git transfer protocol in which Git-aware endpoints negotiate and generate the required object data.
- [Sparse index](https://www.ask-codey.com/glossary/sparse-index): An index that can represent excluded directory trees with single entries instead of listing every file.
- [Split index](https://www.ask-codey.com/glossary/split-index): An index mode that stores shared entries separately so routine index updates can stay smaller.
- [Subtree merge](https://www.ask-codey.com/glossary/subtree-merge): A merge approach that adjusts one project's tree to fit beneath a directory in another project.
- [Tag object](https://www.ask-codey.com/glossary/tag-object): A Git object used by an annotated tag to name another object and store tagger information and a message.
- [Thin pack](https://www.ask-codey.com/glossary/thin-pack): A packfile allowed to depend on base objects expected to exist outside that pack.
- [Tree object](https://www.ask-codey.com/glossary/tree-object): A Git object that records names, modes, and object IDs for files and subdirectories.
- [Unmerged index entry](https://www.ask-codey.com/glossary/unmerged-index-entry): One of the staged base, ours, or theirs records retained for a path with an unresolved conflict.
- [Unreachable object](https://www.ask-codey.com/glossary/unreachable-object): An object that exists locally but cannot be reached from the references being considered.
- [Untracked cache](https://www.ask-codey.com/glossary/untracked-cache): Index extension data that avoids repeatedly scanning unchanged directories for untracked files.

[Read them in the glossary](https://www.ask-codey.com/glossary/subjects/git/master)

Source: https://www.ask-codey.com/decks/git/master
