Skip to main content

Git

PropertyValue
descriptionGit
tagsref
rating

Overview

Git is a distributed version control system used to track changes in code, documentation, and other text-based project files over time.

It matters because it enables branching, merging, history review, collaboration, and rollback without requiring teams to work directly on the same copy of a project at once.

What Git Does

Git stores a history of changes so teams can:

  • see what changed and when
  • compare revisions
  • create branches for isolated work
  • merge completed changes back together
  • recover earlier states when needed

Because the repository history lives with the project, Git supports both solo work and multi-person collaboration without depending on one always-connected central server.

Core Concepts

Common Git concepts include:

  • a repository as the tracked project history
  • commits as saved snapshots of changes
  • branches as parallel lines of work
  • merges and rebases for integrating work
  • remotes such as GitHub for shared collaboration

These concepts are simple in principle, but they shape most modern software and documentation workflows.

Why Git Matters

Git is not just for code. It is also useful for docs, scripts, configuration, and other text-heavy work because it provides traceability and safe iteration.

That is why Git sits close to repo, release, hotfix, and rollback workflows.

Git vs GitHub

Git and GitHub are related but different.

  • Git is the version control system.
  • GitHub is a hosted collaboration platform built around Git repositories.

Other platforms such as GitLab or Bitbucket can also host Git repositories.

Frequently Asked Questions

Is Git only for developers?

No. Writers, operators, designers working with text-based assets, and other contributors can all benefit from version history and collaboration workflows.

Does Git require GitHub?

No. Git works locally on its own. A hosted platform is optional, though common for team collaboration.

Is a commit the same as publishing?

No. A commit records history in the repository. Publishing or deployment is a separate workflow step.

Resources