spb/tools-spboucher-ai

1{2  "slug": "git",3  "name": "Git",4  "aliases": ["git-scm"],5  "vendor": { "name": "Git project (Software Freedom Conservancy)", "slug": "git-project", "website": "https://git-scm.com" },6  "homepage_url": "https://git-scm.com/",7  "docs_url": "https://git-scm.com/doc",8  "repo_url": "https://github.com/git/git",9  "license_url": "https://github.com/git/git/blob/master/COPYING",10  "product_type": "cli-tool",11  "product_status": "active",12  "summary": "Distributed version control system that records snapshots of a project's history locally and synchronizes them with remotes such as GitHub, GitLab or a bare repository over SSH",13  "description": "Git is a distributed version control system created by Linus Torvalds in 2005 and maintained by Junio Hamano and a community of contributors, with the Software Freedom Conservancy as its fiscal home. Every clone holds the full history as a content-addressed object store, so committing, branching, diffing and searching history work offline and remotes are only needed to exchange changes. Branches are lightweight pointers, which makes feature branches, rebases and topic-based workflows cheap.\n\nGit is the substrate for nearly all code hosting: GitHub, GitLab, Gitea and Forgejo are web services built around Git repositories, and self-hosted bare repositories reachable over SSH are a complete remote on their own. Tooling surrounds it at every level, from editor integrations and graphical clients to hooks that run linters or tests, large-file storage (Git LFS) for binary assets, and signing of commits and tags with GPG or SSH keys.\n\nBeyond source code, Git is routinely used to version LaTeX manuscripts, analysis scripts, infrastructure configuration and documentation, giving researchers an audit trail and the ability to reproduce an exact state. The command-line interface is the reference; the official documentation includes the Pro Git book and the reference manual for every subcommand.\n\nIts difficulties are well known: the command vocabulary is inconsistent and the conceptual model (index, working tree, detached HEAD, rebase versus merge) takes time to internalize; large binary files bloat repositories unless LFS is used; and history rewriting on shared branches causes trouble for collaborators. Monorepos at very large scale need additional tooling such as sparse checkout and partial clone.",14  "capabilities": ["Full local history with offline commits, branches and diffs", "Lightweight branching, merging and rebasing", "Remotes over SSH, HTTPS and the Git protocol", "Hooks for automation on commit, push and receive", "Commit and tag signing with GPG or SSH keys", "Partial clone, sparse checkout and worktrees for large repositories", "Bisect, blame and log search for history forensics", "Submodules and Git LFS for dependencies and large files"],15  "workflows": ["Branch, commit and open a pull or merge request on a forge", "Push to a bare repository on a private server over SSH", "Version a LaTeX paper or analysis pipeline alongside its data manifests", "Find the commit that introduced a regression with bisect"],16  "advantages": ["Universal: every forge, editor and CI system supports it", "Works fully offline", "Cheap branching enables flexible workflows", "Free software under the GPL"],17  "limitations": ["Steep conceptual learning curve and inconsistent command design", "Poor handling of large binary files without LFS", "History rewriting on shared branches is error-prone", "Very large monorepos need extra tooling"],18  "prerequisites": ["Any OS; ships with Xcode Command Line Tools on macOS or via package managers"],19  "audiences": ["Software developers", "Researchers versioning manuscripts and code", "Operations teams managing configuration as code"],20  "alternatives": ["github", "gitlab", "gitea"],21  "comparison_notes": "GitHub, GitLab and Gitea are not replacements for Git but hosting services built around it; they add web review, issues, CI and access control to Git's core data model. Choosing among them is a hosting decision (cloud versus self-hosted, license, ecosystem), while Git itself is common to all. Other distributed version control systems such as Mercurial exist but have a much smaller share of hosting and tooling support.",22  "categories": [{ "slug": "version-control", "primary": true }],23  "tags": ["version-control", "cli", "open-source", "ssh"],24  "use_cases": ["collaborate", "write-papers"],25  "operating_systems": ["macos", "linux", "windows"],26  "execution_modes": ["local", "self-hosted"],27  "interfaces": ["cli", "library"],28  "deployment_models": ["desktop", "on-premises"],29  "integrations": ["GitHub", "GitLab", "Gitea", "Forgejo", "VS Code", "Git LFS", "SSH", "GPG"],30  "data_formats": ["Git object store", "patch/diff", "bundle"],31  "languages": ["C", "Shell", "Perl"],32  "source_model": "open-source",33  "license_spdx": "GPL-2.0-only",34  "pricing_model": ["open-source", "free"],35  "self_hostable": true,36  "sources": [37    { "url": "https://git-scm.com/", "type": "official_site", "title": "Git", "supports": ["name", "summary"], "checked_at": "2026-11-02" },38    { "url": "https://git-scm.com/doc", "type": "official_docs", "title": "Git Documentation", "supports": ["capabilities", "description"], "checked_at": "2026-11-02" },39    { "url": "https://github.com/git/git", "type": "repository", "title": "git/git mirror", "supports": ["repo_url"], "checked_at": "2026-11-02" },40    { "url": "https://github.com/git/git/blob/master/COPYING", "type": "license_page", "supports": ["license_spdx", "source_model"], "checked_at": "2026-11-02", "note": "COPYING states GPL v2 only" }41  ],42  "confidence": "high",43  "discovery_method": "editorial-research",44  "depth": "deep",45  "editorial_status": "reviewed",46  "visibility": "public",47  "featured": true,48  "author": "batch-B1"49}50