# Git vocabulary

284 Git terms, from Novice to Master. Start with the basics or jump to a level.

Updated: November 19, 2026

## Novice

- [.git directory](https://www.ask-codey.com/glossary/git-directory): The hidden folder that stores a repository's Git data, including objects, references, and configuration.
- [.gitignore](https://www.ask-codey.com/glossary/gitignore): A file containing patterns for intentionally untracked files that Git should normally ignore.
- [Added line](https://www.ask-codey.com/glossary/added-line): A line present in the newer version of a diff but absent from the older version.
- [Author](https://www.ask-codey.com/glossary/author): The person who wrote the changes in a commit
- [Branch](https://www.ask-codey.com/glossary/branch): A movable name that identifies the latest commit in one line of development.
- [Change](https://www.ask-codey.com/glossary/change): A difference made to a project file, such as adding, editing, or removing content.
- [Clean working tree](https://www.ask-codey.com/glossary/clean-working-tree): A working tree with no tracked changes waiting to be staged or committed.
- [Commit](https://www.ask-codey.com/glossary/commit-git): A saved snapshot of staged changes together with information such as its author, time, and message.
- [Commit history](https://www.ask-codey.com/glossary/commit-history): The connected sequence of commits that records how a repository changed.
- [Commit message](https://www.ask-codey.com/glossary/commit-message): A short explanation stored with a commit to describe why the change was made.
- [Committed file](https://www.ask-codey.com/glossary/committed-file): A file whose contents have been saved in a commit.
- [Committer](https://www.ask-codey.com/glossary/committer): The person who created or last applied a commit to the repository.
- [Current branch](https://www.ask-codey.com/glossary/current-branch): The branch that receives the next commit in the present working tree.
- [Default branch](https://www.ask-codey.com/glossary/default-branch): The branch a repository or remote treats as its primary starting branch.
- [Deleted line](https://www.ask-codey.com/glossary/deleted-line): A line present in the older version of a diff but absent from the newer version.
- [Dirty working tree](https://www.ask-codey.com/glossary/dirty-working-tree): A working tree containing tracked changes that are not yet committed.
- [Distributed version control](https://www.ask-codey.com/glossary/distributed-version-control): A version control model in which each clone normally contains the project files and the complete repository history.
- [File state](https://www.ask-codey.com/glossary/file-state): The current relationship between a file in the working tree, staging area, and latest commit.
- [Git](https://www.ask-codey.com/glossary/git): A distributed version control system that records file changes and lets people work with the same project history.
- [git add](https://www.ask-codey.com/glossary/git-add): Adds selected working-tree changes to the staging area.
- [git clone](https://www.ask-codey.com/glossary/git-clone): Creates a new local repository by copying an existing repository.
- [git commit](https://www.ask-codey.com/glossary/git-commit): Creates a commit from the changes currently in the staging area.
- [git config](https://www.ask-codey.com/glossary/git-config): Reads or changes Git configuration values.
- [Git Credential Manager](https://www.ask-codey.com/glossary/git-credential-manager): The helper that signs Git in to GitHub through your web browser the first time you push, then remembers you, so no password is typed into the terminal.
- [git diff](https://www.ask-codey.com/glossary/git-diff): Shows line-by-line differences between selected versions or file states.
- [git init](https://www.ask-codey.com/glossary/git-init): Creates an empty Git repository in a folder or reinitializes an existing one.
- [git log](https://www.ask-codey.com/glossary/git-log): Displays commits from repository history.
- [git show](https://www.ask-codey.com/glossary/git-show): Displays details and changes for a Git object, usually a commit.
- [git status](https://www.ask-codey.com/glossary/git-status): Shows the current branch and the state of tracked, untracked, and staged files.
- [GitBash](https://www.ask-codey.com/glossary/gitbash): GitBash is a terminal that was created for Windows OS so that users could run standard…
- [GitHub](https://www.ask-codey.com/glossary/github): A website that stores Git repositories online, so you can back up your code and share it.
- [Global Git configuration](https://www.ask-codey.com/glossary/global-git-configuration): Git settings that normally apply to every repository used by one account on a computer.
- [Ignore pattern](https://www.ask-codey.com/glossary/ignore-pattern): A rule that matches files or folders Git should treat as ignored.
- [Index](https://www.ask-codey.com/glossary/index-git): Git's internal name for the data that represents the staging area.
- [Local Git configuration](https://www.ask-codey.com/glossary/local-git-configuration): Git settings stored for one repository and used in preference to matching global settings.
- [Local repository](https://www.ask-codey.com/glossary/local-repository): A Git repository stored on your own computer.
- [Main branch](https://www.ask-codey.com/glossary/main-branch): A commonly used name for a project's primary branch.
- [Modified file](https://www.ask-codey.com/glossary/modified-file): A tracked file whose working-tree contents differ from the recorded version.
- [Repository](https://www.ask-codey.com/glossary/repository): A project and the version-control data used to record its history.
- [Repository root](https://www.ask-codey.com/glossary/repository-root): The top-level folder of a working tree.
- [Snapshot](https://www.ask-codey.com/glossary/snapshot): The complete recorded state of the project at a particular commit.
- [Staged file](https://www.ask-codey.com/glossary/staged-file): A file whose current changes have been placed in the staging area for the next commit.
- [Staging area](https://www.ask-codey.com/glossary/staging-area): The prepared set of changes that will be included in the next commit.
- [Tracked file](https://www.ask-codey.com/glossary/tracked-file): A file Git already knows about and can include in future snapshots.
- [Untracked file](https://www.ask-codey.com/glossary/untracked-file): A file in the working tree that Git has not been told to track.
- [user.email](https://www.ask-codey.com/glossary/user-email): The Git configuration value recorded as the author or committer email address.
- [user.name](https://www.ask-codey.com/glossary/user-name): The Git configuration value recorded as the human-readable author or committer name.
- [Version control](https://www.ask-codey.com/glossary/version-control): A way to record changes to files so earlier versions can be compared or restored.
- [Working directory](https://www.ask-codey.com/glossary/working-directory): The folder where you run Git commands and work with checked-out project files.
- [Working tree](https://www.ask-codey.com/glossary/working-tree): The checked-out files and folders that you can currently view and edit.

## Apprentice

- [Abort an operation](https://www.ask-codey.com/glossary/abort-an-operation): Stops an in-progress Git operation and tries to return the repository to its earlier state.
- [Ahead](https://www.ask-codey.com/glossary/ahead): A branch is ahead when it contains commits that its comparison branch does not contain.
- [Annotated tag](https://www.ask-codey.com/glossary/annotated-tag): A tag stored as its own object with a message, tagger details, and optional signature.
- [Behind](https://www.ask-codey.com/glossary/behind): A branch is behind when its comparison branch contains commits that it does not contain.
- [Branch name](https://www.ask-codey.com/glossary/branch-name): The human-readable name used to refer to a branch.
- [Branch tip](https://www.ask-codey.com/glossary/branch-tip): The latest commit currently identified by a branch.
- [Centralized Version Control](https://www.ask-codey.com/glossary/centralized-version-control): A version control model where one central server holds the project's only full history.
- [Commit amendment](https://www.ask-codey.com/glossary/commit-amendment): Replacing the latest commit with a new commit containing corrected content or metadata.
- [Conflict marker](https://www.ask-codey.com/glossary/conflict-marker): Text Git places in a conflicted file to show the competing versions that must be resolved.
- [Conflict resolution](https://www.ask-codey.com/glossary/conflict-resolution): The chosen final content that replaces competing changes in a merge or rebase conflict.
- [Continue an operation](https://www.ask-codey.com/glossary/continue-an-operation): Resumes a paused Git operation after required conflicts or edits have been completed.
- [Discard changes](https://www.ask-codey.com/glossary/discard-changes): Replaces uncommitted edits with a chosen recorded version, permanently removing those edits.
- [Diverged branches](https://www.ask-codey.com/glossary/diverged-branches): Branches that each contain commits missing from the other branch.
- [Executable bit](https://www.ask-codey.com/glossary/executable-bit): A tracked permission flag indicating that a file should be treated as executable on supporting systems.
- [Fast-forward merge](https://www.ask-codey.com/glossary/fast-forward-merge): A merge completed by moving the current branch forward because it has no separate new commits.
- [Feature branch](https://www.ask-codey.com/glossary/feature-branch): A branch used to develop one feature separately from the main line of work.
- [Fetch](https://www.ask-codey.com/glossary/fetch): The operation that downloads new objects and reference information from a remote.
- [git branch](https://www.ask-codey.com/glossary/git-branch): Lists, creates, renames, or deletes branches without switching the working tree.
- [git checkout](https://www.ask-codey.com/glossary/git-checkout): Restores selected files or switches branches using Git's older multipurpose command.
- [git fetch](https://www.ask-codey.com/glossary/git-fetch): Downloads objects and references from a remote without changing the current branch.
- [git merge](https://www.ask-codey.com/glossary/git-merge): Combines changes from another line of development into the current branch.
- [git mv](https://www.ask-codey.com/glossary/git-mv): Moves or renames a path and stages the resulting changes.
- [git pull](https://www.ask-codey.com/glossary/git-pull): Fetches from a remote and then integrates the fetched branch into the current branch.
- [git push](https://www.ask-codey.com/glossary/git-push): Sends local objects and reference updates to a remote repository.
- [git remote](https://www.ask-codey.com/glossary/git-remote): Views and manages the saved names and URLs of remote repositories.
- [git restore](https://www.ask-codey.com/glossary/git-restore): Restores file contents in the working tree or removes changes from the staging area.
- [git revert](https://www.ask-codey.com/glossary/git-revert): Creates a new commit that reverses changes introduced by an earlier commit.
- [git rm](https://www.ask-codey.com/glossary/git-rm): Removes a tracked path from the working tree and stages the removal.
- [git stash](https://www.ask-codey.com/glossary/git-stash): Temporarily stores selected uncommitted changes and returns those files toward a clean state.
- [git stash apply](https://www.ask-codey.com/glossary/git-stash-apply): Applies a stash entry while keeping the entry in the stash.
- [git stash drop](https://www.ask-codey.com/glossary/git-stash-drop): Deletes a selected stash entry without applying it.
- [git stash pop](https://www.ask-codey.com/glossary/git-stash-pop): Applies the latest or selected stash entry and removes it if the application succeeds.
- [git switch](https://www.ask-codey.com/glossary/git-switch): Changes the current branch or creates and switches to a new branch.
- [git tag](https://www.ask-codey.com/glossary/git-tag): Lists, creates, verifies, or deletes tags.
- [Lightweight tag](https://www.ask-codey.com/glossary/lightweight-tag): A tag that stores only a reference to an existing object.
- [Merge commit](https://www.ask-codey.com/glossary/merge-commit): A commit with multiple parents that joins lines of development.
- [Merge conflict](https://www.ask-codey.com/glossary/merge-conflict): A situation in which Git cannot safely combine competing changes without a person's decision.
- [Origin](https://www.ask-codey.com/glossary/origin): The default remote name Git usually creates when a repository is cloned.
- [Push](https://www.ask-codey.com/glossary/push-git): The operation that sends local commits and reference updates to a remote.
- [Remote](https://www.ask-codey.com/glossary/remote): A saved name and URL for another Git repository.
- [Remote repository](https://www.ask-codey.com/glossary/remote-repository): A repository known through a URL and commonly used to exchange commits with other copies.
- [Remote URL](https://www.ask-codey.com/glossary/remote-url): The location Git uses to contact a remote repository.
- [Remote-tracking branch](https://www.ask-codey.com/glossary/remote-tracking-branch): A local reference that records the last known position of a branch in a remote repository.
- [Revert commit](https://www.ask-codey.com/glossary/revert-commit): A commit whose changes reverse all or part of another commit.
- [Stash entry](https://www.ask-codey.com/glossary/stash-entry): One saved set of uncommitted changes in the stash.
- [Tag](https://www.ask-codey.com/glossary/tag): A named reference commonly used to mark one important point in history.
- [Topic branch](https://www.ask-codey.com/glossary/topic-branch): A short-lived branch used for one focused change, such as a feature or bug fix.
- [Tracking branch](https://www.ask-codey.com/glossary/tracking-branch): A local branch configured with an upstream branch for status, pull, and push operations.
- [Unstage](https://www.ask-codey.com/glossary/unstage): Removes changes from the staging area while normally leaving the working-tree edits in place.
- [Upstream branch](https://www.ask-codey.com/glossary/upstream-branch): The branch a local branch is configured to compare with and normally pull from.
- [Upstream remote](https://www.ask-codey.com/glossary/upstream-remote): A remote treated as the source repository from which changes are received.

## Journeyman

- [Ancestor](https://www.ask-codey.com/glossary/ancestor-git): An earlier commit reachable by repeatedly following parent links.
- [Bisect bad revision](https://www.ask-codey.com/glossary/bisect-bad-revision): A revision marked as containing the problem being investigated.
- [Bisect good revision](https://www.ask-codey.com/glossary/bisect-good-revision): A revision marked as not containing the problem being investigated.
- [Caret revision syntax](https://www.ask-codey.com/glossary/caret-revision-syntax): Revision syntax that selects a parent or excludes commits from a set.
- [Client-side hook](https://www.ask-codey.com/glossary/client-side-hook): A hook that runs in a contributor's local repository.
- [Commit graph](https://www.ask-codey.com/glossary/commit-graph): The connected structure formed by commits and their parent relationships.
- [Commit hash](https://www.ask-codey.com/glossary/commit-hash): A hexadecimal identifier used to refer to a particular commit object.
- [Commit-msg hook](https://www.ask-codey.com/glossary/commit-msg-hook): A client-side hook that can inspect or reject a proposed commit message.
- [Common ancestor](https://www.ask-codey.com/glossary/common-ancestor): A commit reachable from each of two or more commits by following parent links.
- [Context line](https://www.ask-codey.com/glossary/context-line): An unchanged line included around a change to show where the change belongs.
- [Descendant commit](https://www.ask-codey.com/glossary/descendant-commit): A later commit that can reach another commit by following its parent links.
- [Detached HEAD](https://www.ask-codey.com/glossary/detached-head): A state in which HEAD points directly to a commit instead of to a branch.
- [Diff hunk](https://www.ask-codey.com/glossary/diff-hunk): A grouped section of nearby changed lines in a diff.
- [Drop a commit](https://www.ask-codey.com/glossary/drop-a-commit): Removes a selected commit while rewriting history during an interactive rebase.
- [Fixup](https://www.ask-codey.com/glossary/fixup): Combines a commit with an earlier commit while normally discarding the fixup commit's message.
- [Force push](https://www.ask-codey.com/glossary/force-push): A push that permits a remote branch to lose commits not present in the proposed update.
- [Force with lease](https://www.ask-codey.com/glossary/force-with-lease): A guarded force push that fails if the remote reference no longer has the expected value.
- [git am](https://www.ask-codey.com/glossary/git-am): Applies mailbox-formatted patches and creates commits from them.
- [git apply](https://www.ask-codey.com/glossary/git-apply): Applies changes from a patch to files without creating a commit.
- [git bisect](https://www.ask-codey.com/glossary/git-bisect): Uses binary search through history to help find the commit that introduced a problem.
- [git blame](https://www.ask-codey.com/glossary/git-blame): Shows which commit and author last changed each line of a file.
- [git cherry-pick](https://www.ask-codey.com/glossary/git-cherry-pick): Applies the changes introduced by selected commits as new commits on the current branch.
- [git clean](https://www.ask-codey.com/glossary/git-clean): Removes selected untracked files or folders from the working tree.
- [git format-patch](https://www.ask-codey.com/glossary/git-format-patch): Creates email-ready patch files from commits.
- [Git hook](https://www.ask-codey.com/glossary/git-hook): A program Git runs when a particular repository event occurs.
- [git rebase](https://www.ask-codey.com/glossary/git-rebase): Replays commits onto a new base and replaces them with newly created commits.
- [git reflog](https://www.ask-codey.com/glossary/git-reflog): Shows recent updates to local references, including earlier positions of HEAD and branches.
- [git reset](https://www.ask-codey.com/glossary/git-reset): Moves a branch or adjusts the index and working tree to match a selected commit, depending on its mode.
- [Hard reset](https://www.ask-codey.com/glossary/hard-reset): A reset that moves the current branch and replaces tracked index and working-tree content.
- [HEAD](https://www.ask-codey.com/glossary/head): The reference that identifies the currently checked-out branch or commit.
- [Hunk header](https://www.ask-codey.com/glossary/hunk-header): The line that identifies the old and new line ranges covered by a diff hunk.
- [Interactive rebase](https://www.ask-codey.com/glossary/interactive-rebase): A rebase that lets you reorder, combine, edit, rename, or remove selected commits.
- [Merge base](https://www.ask-codey.com/glossary/merge-base): A best common ancestor used as the starting point for a merge.
- [Mixed reset](https://www.ask-codey.com/glossary/mixed-reset): A reset that moves the current branch and resets the index while leaving working-tree files unchanged.
- [Object ID](https://www.ask-codey.com/glossary/object-id): The hash-based identifier Git uses to name an object.
- [Ours](https://www.ask-codey.com/glossary/ours): The version associated with the current side of a merge, though its exact meaning can vary by operation.
- [Parent commit](https://www.ask-codey.com/glossary/parent-commit): A commit named by a later commit as its immediate history.
- [Patch](https://www.ask-codey.com/glossary/patch): A text representation of changes that can be reviewed, shared, or applied.
- [Pre-commit hook](https://www.ask-codey.com/glossary/pre-commit-hook): A client-side hook that runs before Git creates a commit.
- [Pre-push hook](https://www.ask-codey.com/glossary/pre-push-hook): A client-side hook that runs before objects and reference updates are sent to a remote.
- [Rebase todo list](https://www.ask-codey.com/glossary/rebase-todo-list): The ordered instructions Git follows during an interactive rebase.
- [Ref](https://www.ask-codey.com/glossary/ref): Git's short term for a reference such as a branch, tag, or remote-tracking branch.
- [Reference](https://www.ask-codey.com/glossary/reference): A stored name that points to an object ID, usually a commit.
- [Reflog entry](https://www.ask-codey.com/glossary/reflog-entry): A local record of one update made to a reference.
- [Relative reference](https://www.ask-codey.com/glossary/relative-reference): A reference expression that selects another commit relative to a known reference.
- [Revision](https://www.ask-codey.com/glossary/revision): A commit or other object selected by a revision expression.
- [Revision range](https://www.ask-codey.com/glossary/revision-range): An expression that selects commits by describing relationships between revisions.
- [Reword](https://www.ask-codey.com/glossary/reword): Changes a commit message while keeping the commit's file changes.
- [Root commit](https://www.ask-codey.com/glossary/root-commit): A commit with no parent, normally representing the beginning of a repository's history.
- [Server-side hook](https://www.ask-codey.com/glossary/server-side-hook): A hook that runs in a repository receiving network operations.
- [SHA](https://www.ask-codey.com/glossary/sha): An informal name for a Git object ID, based on the hash algorithms Git has historically used.
- [Signature verification](https://www.ask-codey.com/glossary/signature-verification): The process of checking that a Git signature is valid and associated with a trusted identity.
- [Signed commit](https://www.ask-codey.com/glossary/signed-commit): A commit containing a cryptographic signature that can be checked against its contents.
- [Signed tag](https://www.ask-codey.com/glossary/signed-tag): An annotated tag containing a cryptographic signature.
- [Soft reset](https://www.ask-codey.com/glossary/soft-reset): A reset that moves the current branch while leaving the index and working tree unchanged.
- [Squash](https://www.ask-codey.com/glossary/squash): Combines a commit with the preceding commit during an interactive rebase.
- [Symbolic reference](https://www.ask-codey.com/glossary/symbolic-reference): A reference that points to another reference rather than directly to an object ID.
- [Theirs](https://www.ask-codey.com/glossary/theirs): The version associated with the other side of a merge, though its exact meaning can vary by operation.
- [Three-way merge](https://www.ask-codey.com/glossary/three-way-merge): A merge that compares two branch tips with their common ancestor.
- [Tilde revision syntax](https://www.ask-codey.com/glossary/tilde-revision-syntax): Revision syntax that follows a commit's first-parent chain a chosen number of times.

## Freelancer

- [.gitattributes](https://www.ask-codey.com/glossary/gitattributes): A file containing Git attribute rules for paths in a repository.
- [Ancestry path](https://www.ask-codey.com/glossary/ancestry-path): A revision selection limited to commits that connect chosen descendants to chosen ancestors.
- [Atomic ref update](https://www.ask-codey.com/glossary/atomic-ref-update): A reference change that either completes as one protected operation or does not take effect.
- [Attribute pattern](https://www.ask-codey.com/glossary/attribute-pattern): The path-matching portion of a Git attributes rule.
- [Bare repository](https://www.ask-codey.com/glossary/bare-repository): A repository with no working tree, commonly used as a shared remote.
- [Clean filter](https://www.ask-codey.com/glossary/clean-filter): A content filter applied when data moves from the working tree toward the object database.
- [Cone mode](https://www.ask-codey.com/glossary/cone-mode): A sparse-checkout mode optimized for selecting whole directory trees.
- [Copy detection](https://www.ask-codey.com/glossary/copy-detection): Git's comparison process for identifying a new path whose content came from an existing path.
- [Diff driver](https://www.ask-codey.com/glossary/diff-driver): A configured rule that changes how Git compares or displays selected files.
- [Directed acyclic graph](https://www.ask-codey.com/glossary/directed-acyclic-graph): A graph whose links have direction and cannot form a path back to the same starting point.
- [End-of-line normalization](https://www.ask-codey.com/glossary/end-of-line-normalization): Storing chosen text files with consistent line endings while allowing configured working-tree endings.
- [Exclude pathspec](https://www.ask-codey.com/glossary/exclude-pathspec): A pathspec that removes matching paths after positive pathspecs have selected candidates.
- [Fetch refspec](https://www.ask-codey.com/glossary/fetch-refspec): A refspec that controls which remote references are fetched and where they are stored locally.
- [First-parent history](https://www.ask-codey.com/glossary/first-parent-history): A view of history that follows only the first parent of each merge commit.
- [git archive](https://www.ask-codey.com/glossary/git-archive): Creates an archive of files from a selected tree without including repository history.
- [Git attributes](https://www.ask-codey.com/glossary/git-attributes): Per-path settings that control behavior such as text handling, diffs, merges, and export.
- [Git bundle](https://www.ask-codey.com/glossary/git-bundle): A single file that carries Git objects and references for transfer without a live remote connection.
- [git for-each-ref](https://www.ask-codey.com/glossary/git-for-each-ref): Formats and displays references selected from one or more reference namespaces.
- [git merge-base](https://www.ask-codey.com/glossary/git-merge-base): Finds best common ancestors between commits.
- [Git notes](https://www.ask-codey.com/glossary/git-notes): Extra information attached to objects without changing the objects themselves.
- [git rerere](https://www.ask-codey.com/glossary/git-rerere): Records conflict resolutions and can reuse them when the same conflict appears again.
- [git rev-list](https://www.ask-codey.com/glossary/git-rev-list): Lists commit objects reachable under selected revision and traversal rules.
- [git rev-parse](https://www.ask-codey.com/glossary/git-rev-parse): Interprets revision and option syntax and can return object IDs or repository information.
- [git update-ref](https://www.ask-codey.com/glossary/git-update-ref): Safely creates, updates, or deletes references while checking expected values when requested.
- [Histogram diff](https://www.ask-codey.com/glossary/histogram-diff): A diff algorithm that extends patience-style matching by considering low-occurrence lines.
- [Linked worktree](https://www.ask-codey.com/glossary/linked-worktree): An additional worktree connected to the same repository data as another worktree.
- [Magic pathspec](https://www.ask-codey.com/glossary/magic-pathspec): A pathspec using special controls for matching behavior such as case sensitivity or exclusions.
- [Mailmap](https://www.ask-codey.com/glossary/mailmap): A file or configuration that maps alternate author identities to preferred names and email addresses.
- [Main worktree](https://www.ask-codey.com/glossary/main-worktree): The original worktree created with a normal repository, rather than one added later.
- [Merge driver](https://www.ask-codey.com/glossary/merge-driver): A configured program or built-in behavior used to merge selected file types.
- [Minimal diff](https://www.ask-codey.com/glossary/minimal-diff): A diff mode that spends extra time trying to produce the smallest possible change set.
- [--mirror clone](https://www.ask-codey.com/glossary/mirror-clone): A bare clone that maps all references from the source and configures matching mirror updates.
- [Missing object](https://www.ask-codey.com/glossary/missing-object): An object referenced by repository data but not currently available in the local object database.
- [Myers diff](https://www.ask-codey.com/glossary/myers-diff): Git's default general-purpose algorithm for finding a short edit sequence between file versions.
- [Namespace](https://www.ask-codey.com/glossary/namespace-git): A reference prefix that lets one repository expose separated groups of references.
- [Negative refspec](https://www.ask-codey.com/glossary/negative-refspec): A fetch refspec beginning with an exclusion that removes matching references from a broader selection.
- [Notes ref](https://www.ask-codey.com/glossary/notes-ref): A reference whose commits store notes attached to other Git objects.
- [Partial clone](https://www.ask-codey.com/glossary/partial-clone): A clone that can omit selected reachable objects and request them later when needed.
- [Pathspec](https://www.ask-codey.com/glossary/pathspec): A Git expression that selects paths for a command.
- [Patience diff](https://www.ask-codey.com/glossary/patience-diff): A diff algorithm that anchors on unique lines to make some changes easier to read.
- [Promisor remote](https://www.ask-codey.com/glossary/promisor-remote): A remote that promises it can supply objects intentionally omitted from a partial clone.
- [Push refspec](https://www.ask-codey.com/glossary/push-refspec): A refspec that controls which local references update which references on a remote.
- [Recorded resolution](https://www.ask-codey.com/glossary/recorded-resolution): A conflict resolution saved by rerere for possible reuse.
- [Refspec](https://www.ask-codey.com/glossary/refspec): A pattern describing which source references map to which destination references during fetch or push.
- [Rename detection](https://www.ask-codey.com/glossary/rename-detection): Git's comparison process for pairing a deleted path with a sufficiently similar added path.
- [Replace ref](https://www.ask-codey.com/glossary/replace-ref): A reference that tells Git to read one object as a replacement for another object.
- [Repository mirror](https://www.ask-codey.com/glossary/repository-mirror): A repository copy configured to reproduce all selected references from another repository.
- [Revision walk](https://www.ask-codey.com/glossary/revision-walk): The process of traversing commits from starting revisions while applying ordering and limiting rules.
- [Shallow clone](https://www.ask-codey.com/glossary/shallow-clone): A clone created with only a limited portion of reachable commit history.
- [Shallow repository](https://www.ask-codey.com/glossary/shallow-repository): A repository whose history intentionally stops at recorded shallow boundary commits.
- [Smudge filter](https://www.ask-codey.com/glossary/smudge-filter): A content filter applied when data moves from the object database into the working tree.
- [Sparse checkout](https://www.ask-codey.com/glossary/sparse-checkout): A working-tree arrangement that populates only selected paths from the current commit.
- [Submodule](https://www.ask-codey.com/glossary/submodule): A repository recorded inside another repository through a path and a specific commit.
- [Submodule commit](https://www.ask-codey.com/glossary/submodule-commit): The specific commit of a submodule recorded by its superproject.
- [Superproject](https://www.ask-codey.com/glossary/superproject): A repository that records one or more submodules.
- [Text attribute](https://www.ask-codey.com/glossary/text-attribute): An attribute that tells Git whether a path should receive text and line-ending processing.
- [Topological order](https://www.ask-codey.com/glossary/topological-order): A commit order that avoids showing a parent before any displayed descendant.
- [Word diff](https://www.ask-codey.com/glossary/word-diff): A diff display that highlights changed words instead of only changed lines.
- [Working-tree encoding](https://www.ask-codey.com/glossary/working-tree-encoding): An attribute describing the character encoding a file should use in the working tree.
- [Worktree](https://www.ask-codey.com/glossary/worktree): A checked-out set of repository files associated with its own HEAD and index.

## Master

- [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.

[More subjects in Cloud & DevOps](https://www.ask-codey.com/glossary/groups/cloud-and-devops)

Source: https://www.ask-codey.com/glossary/subjects/git
