Git

git-scm.com ↗

Track project history locally, branch freely, and share selected commits with collaborators.

SI Score
80/100
Pricing
Open Source AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Not confirmed

Ask SI about Git

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Git homepage

What it does

Git is a distributed version control system for tracking changes to source code and other files. Developers can commit history locally, create branches, compare changes, and exchange work with a remote repository. The command-line tool and its official tutorial cover the core workflow, while repository hosting is provided by separate services.

Start with a local repository

The official tutorial creates a repository, adds files to the index, and records a first commit. From there, a developer can inspect history and create a branch for a change before merging it back. Git's distributed design keeps local history and branch work available without a network connection; collaboration begins when a remote repository is configured and changes are fetched or pushed.

A useful habit is to review the staged diff before recording a commit, especially when a working tree contains generated files or unrelated edits. Git is a version-control engine, not a hosting site or a graphical editor, so teams still choose their own review and repository-hosting workflow. The official source license is GPLv2.

Strengths

  • Local commits and branches support offline work before sharing changes.
  • The official tutorial explains a path from a new repository to collaboration and branch management.
  • The project has a broad ecosystem of command-line tools and graphical clients.

Watch out for

  • Repository hosting, code review, and issue tracking are separate choices rather than features of the Git command-line tool.
  • The staged index adds a step between editing files and committing them, so users need to understand what is being recorded.

Best for

  • Developers who need a distributed history for source code or other changing files.
  • Teams choosing their own repository hosting and review workflow.

Sources