# Git vocabulary: Journeyman level

60 Git terms at the Journeyman level, each with a short definition and a link to its full page.

Updated: November 17, 2026

[Study these as flash cards](https://www.ask-codey.com/decks/git/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.

- Previous level: [Apprentice](https://www.ask-codey.com/glossary/subjects/git/apprentice)
- Next level: [Freelancer](https://www.ask-codey.com/glossary/subjects/git/freelancer)

[Every Git term, by level](https://www.ask-codey.com/glossary/subjects/git)

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