Git
Editor’s pickVersion control
Free, open-source version control system and the foundation for collaborating on code, scripts and paper projects.
- Main category
- Version control
- Cost
- See the official site for cost
- Licence type
- Open source
- Platforms
- Windows / macOS / Linux
Version-watched: add it to favourites and confirmed new releases will show on your favourites page (stored in this browser only).
Editor’s pick for Coding & data · Version control
- Good for
- Researchers who want a history of changes to analysis scripts and manuscript sources, so others can reproduce the work.
- Why it is recommended
- An open-source (GPL version 2) distributed version control system: record every change, compare versions and restore earlier ones — a basic tool for keeping an analysis reproducible.
- Limits and when to choose something else
- Mainly used from the command line; you need to learn commits and branches. Not suited to managing large binary data files directly. Never commit files containing personal data, passwords or keys to a public repository.
Sources checked: 2026-11-05 · Compiled from official sources; not run by ZIRULAB
Practical notes
Typical uses
- Versioning analysis scripts, LaTeX / Markdown manuscripts and configuration files.
- Collaborating and keeping backups through GitHub, GitLab and similar platforms.
Good for
- Research projects that need to trace which version of the code produced which result.
Less suited / consider instead
- Our suggestion: large raw data (images, video, model output) usually does not belong directly in Git; use a data repository or a dedicated tool.
Technical limits and cautions
- You need to learn basic commands and concepts (commit, branch, merge). The official site offers the Pro Git book online under CC BY-NC-SA 3.0.
Official getting-started docs: Pro Git (official online book)
Compiled from the official pages below (read 2026-11-05); not run by us. The “less suited” items are our suggestions.
Details
Git is the most widely used distributed version control system, tracking the change history of code, scripts, documents and project files. In research it suits managing analysis scripts, software development, paper versions and team collaboration.
Use cases: code version control, paper project management, script backup, team collaboration