# Git

Distributed history and branches for local work with a separate choice of hosting.

ID: git
Language: en
Revision: 1
Translation source revision: 1
Canonical: https://kickoff.jujin.dev/en/catalog/git/

## Why: the goal or problem

A travel website lets friends arrange daily stops. Its developers need separate experiments while offline. They want local history and Git-compatible hosting; keeping existing SVN tooling would favor Subversion instead.

## How: work toward a solution

Commit a new stop on a local branch. The remote still lacks it. Push that branch when connected, then a teammate fetches it. Check both histories; a rejected push needs reconciliation.

## What: the concept

Git is a distributed version control system. Commit records locally; push shares with another repository. GitHub and other hosts add collaboration around Git. Conflicts still need judgment.

[Source](https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control)

---

# Go further

Optional reading · separate from the overview

## Selection & comparison

Compare history location, offline work, collaboration, file types and existing tools. Git keeps a local repository for commits and branches. Mercurial also supports distributed work; preserving an established hg workflow can outweigh migration. SVN retains central commits; P4 may fit a team already managing exclusive edits of binary assets.

## Applications

The travel site tries a museum stop on its own branch. A local commit survives closing the editor but is absent from the shared repository until a successful push. A teammate fetches it before reviewing or integrating it. Git hosting is a separate choice: these catalog hosts work with Git, not as interchangeable servers for every version control system.

## Implementation & cautions

Inspect git status and the intended branch before committing. Confirm the remote and access before pushing; reconcile diverged history rather than forcing over teammates. A Git clone does not automatically preserve hosting issues, reviews or settings. Test their export separately when changing hosts.

## Evidence

- [Pro Git: About Version Control](https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control) — Local and distributed history models. (Checked: 2026-09-27)
- [Pro Git: Working with Remotes](https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes) — Fetching and pushing exchange repository data; pushing requires access and compatible history. (Checked: 2026-09-27)