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