Vibulary
Menu
Appearance and language
Terms by topic · 42 guides

Git & Delivery

Learn how to track code changes, work with a team, check updates, and release safely.

01 / Atlas

All Git & Delivery terms

Open a term for a simple meaning, an example, when to use it, how official it is, and its code name.

  1. 01 · Core

    .gitignore

    A .gitignore file lists path patterns Git should leave untracked. Those files stay out of status and new commits.

  2. 02 · Core

    Application Container

    An application container is an instance created from a container image. When started, it runs isolated processes with chosen settings and limits.

  3. 03 · More detail

    Blue-Green Deployment

    A blue-green deployment keeps the current and new versions in separate environments. Traffic switches after the new environment is checked.

  4. 04 · More detail

    Canary Deployment

    A canary deployment sends a small share of real users or traffic to a new version first. Evidence decides whether to expand or stop.

  5. 05 · Core

    Container Image

    A container image is a layered package used to create containers. After a build, its content stays fixed.

  6. 06 · More detail

    Container Orchestration

    Container orchestration automates container work across several machines. It places work, keeps the requested count, replaces failures, and connects services.

  7. 07 · Core

    Container Registry

    A container registry is a service that stores and shares container images. Repositories group related content inside the registry.

  8. 08 · Core

    Continuous Integration

    Continuous integration (CI) means adding small changes to shared code often and checking them with repeatable automation.

  9. 09 · Core

    Deployment Environment

    A deployment environment is a named place or stage where software runs. It has its own settings, credentials, protection rules, deployment history, and live state. It is not a Git object.

  10. 10 · More detail

    Deployment Rollback

    A deployment rollback is a controlled recovery from a failed or unsafe release. It restores a known-good app version and matching state. Exact steps depend on the delivery system and data changes.

  11. 11 · More detail

    Deployment, Environments & Rollback

    These delivery practices move a tested version through separate environments. They also keep a safe way to return to an earlier state.

  12. 12 · More detail

    Detached HEAD

    Detached HEAD is a Git state where HEAD points straight to one commit instead of a branch name.

  13. 13 · More detail

    Git Bisect

    Git bisect uses binary search through commit history to find the first commit where a repeatable behavior changed.

  14. 14 · More detail

    Git Blame

    Git blame shows the latest commit that changed each line of a file. It is a starting point for learning the line's history.

  15. 15 · Core

    Git Branch

    A Git branch is a named pointer that can move from one commit to the next. When new commits are made on that checked-out branch, the pointer moves forward.

  16. 16 · More detail

    Git Cherry-pick

    Git cherry-pick copies the change from one or more chosen commits onto the current branch. It records new commits with new IDs there.

  17. 17 · Core

    Git Clone

    Git Clone makes a local copy of a repository. It copies objects and references, sets a remote, and checks out working files.

  18. 18 · Core

    Git Commit

    A Git commit is a saved object that cannot be changed in place. It records a file tree, parent commits, author and committer details, and a message. Its ID comes from its content.

  19. 19 · Core

    Git Diff

    Git Diff shows exact content changes between two Git states. It can compare working files, the index, commits, or branches.

  20. 20 · Core

    Git Fetch

    Git fetch downloads commits and references from another repository. It updates remote-tracking names but does not put those changes into the current branch.

  21. 21 · More detail

    Git Hook

    A Git hook is a program Git runs at a named step on a developer's computer or server. It can check, block, or automate an action.

  22. 22 · More detail

    Git LFS

    Git LFS is an add-on for large files. Git stores a small pointer, while a separate LFS service stores and sends the full file.

  23. 23 · Core

    Git Merge

    Git Merge joins branch histories. Git may move a pointer forward or create a merge commit after conflicts are resolved.

  24. 24 · Core

    Git Pull

    Git Pull fetches remote updates, then joins the chosen upstream branch into the current branch by merge or rebase.

  25. 25 · Core

    Git Push

    Git Push sends local Git data to a remote repository. It asks the remote to update a named branch or reference.

  26. 26 · More detail

    Git Rebase

    Git rebase moves a line of commits onto a different starting commit. Git replays the changes and gives each replayed commit a new ID.

  27. 27 · Core

    Git Remote

    A Git remote is a named link from a local repository to another repository URL. It lets Git fetch changes and, when allowed, push them.

  28. 28 · Core

    Git Repository

    A Git repository stores a project's version history as Git objects, references, and settings. It may also include a staging area and working files.

  29. 29 · More detail

    Git Reset

    Git reset moves the current branch pointer to another commit. Its mode may also change the staging area and working files to match.

  30. 30 · Core

    Git Revert

    Git revert makes a new commit that undoes the changes from an older commit. It keeps the old history instead of deleting it.

  31. 31 · Core

    Git Stash

    Git Stash temporarily saves chosen uncommitted working-tree and index changes. Saved sets form a stack and can be restored later.

  32. 32 · More detail

    Git Submodule

    A Git submodule lets one repository point to one exact commit in another Git repository. The parent repository also stores how to find it.

  33. 33 · Core

    Git Tag

    A Git tag is a name that points to one exact object, often a release commit. An annotated tag can also store who made it, a message, a date, and a signature.

  34. 34 · More detail

    Git Worktree

    A Git Worktree is another folder linked to one repository. It lets several branches stay open at once.

  35. 35 · Core

    Git, Repository, Branch & Commit — Learning Bundle

    This learning bundle connects four Git ideas. Git's the version-control system. A repository stores its objects and references. A branch names a line of work. A commit records a project state with metadata. The bundle is not one Git term.

  36. 36 · More detail

    Infrastructure as Code

    Infrastructure as code manages infrastructure through machine-readable files instead of only manual clicks. Teams can version, review, test, and apply those files.

  37. 37 · Core

    Merge Conflict

    A merge conflict happens when Git cannot safely combine competing changes by itself. A person or tool must choose the intended final result.

  38. 38 · Core

    Pull Request

    A pull request is a record on a code-hosting site. It asks people to review one branch before adding its changes to a base branch.

  40. 40 · More detail

    Rolling Deployment

    A rolling deployment replaces old application instances with new ones in batches. Each step changes only part of the running group, so versions may overlap.

  41. 41 · Core

    Software Release

    A software release is a version prepared and shared on purpose. It has known files, notes, source records, and clear support expectations.

  42. 42 · More detail

    Squash Commit

    Squashing combines the changes from several commits into one new commit, often with interactive rebase or a merge rule.