Open Source Version Control Software - Page 38
Sort By:
Version Control Software
View 80 business solutions-
Our Free Plans just got better! | Auth0You asked, we delivered! Auth0 is excited to expand our Free and Paid plans to include more options so you can focus on building, deploying, and scaling applications without having to worry about your security. Auth0 now, thank yourself later.
-
Train ML Models With SQL You Already KnowBuild and deploy ML models using familiar SQL. Automate data prep with built-in Gemini. Query 1 TB and store 10 GB free monthly.
-
1
A simple update programm. The update provider can publish a file with the changes on a certain url and if the programm is run it get's new files, creates directories and removes old files according to the update informations.
-
2
"eccvs" is a GUI based version control system (for linux) that keeps track of all the resources of a software project. Here resources mean source code, documentation, etc., This software is based on the existing CVS command line tool.
-
3
-
4
evofetch
Mining tool for software repositories
EvoFETCH is a tool to extract information about software entities such as classes, methods, and attributes from software repositories. EvoFETCH is middleware and makes use of other freely available software to perform the extraction and provide query functionality. -
MongoDB Atlas runs apps anywhereMongoDB Atlas gives you the freedom to build and run modern applications anywhere—across AWS, Azure, and Google Cloud. With global availability in over 115 regions, Atlas lets you deploy close to your users, meet compliance needs, and scale with confidence across any geography.
-
5
exa
A modern replacement for ls
You list files hundreds of times a day. Why spend your time squinting at black and white text? exa is an improved file lister with more features and better defaults. It uses colours to distinguish file types and metadata. It knows about symlinks, extended attributes, and Git. And it’s small, fast, and just one single binary. Different types of file and data will be coloured differently, and the user and group columns will be highlighted for the current user. exa can display a file’s extended attributes, as well as standard filesystem information such as the inode, the number of blocks, and a file’s various dates and times. exa queries files in parallel, giving you performance on par with ls. Not only is the standard tree tool built-in, but it’ll show you your files’ information alongside the hierarchy. View the staged and unstaged status of every file, right there in the standard view. Also works in tree view for a high-level overview of your repository. -
6
forgit
A utility tool powered by fzf for using git interactively
This tool is designed to help you use git more efficiently. It's lightweight and easy to use. Fig adds apps, shortcuts, and autocomplete to your existing terminal. Options can be set via environment variables. They have to be exported in order to be recognized by forgit. You can use forgit as a subcommand of git by making git-forgit available in $PATH. Forgit will use the default configured pager from git (core.pager, pager.show, pager.diff) but can be altered with several environment variables. You can add default fzf options for forgit, including keybinds, layout, etc. (No need to repeat the options already defined. -
7
-
8
The fscvs is a group of tools to generate fspatch from the two filesystems, apply fspatch to generate one filesystems from another, manage filesystem project. A fspatch is a file which contain all of the difference in the compared two filesystems.
-
9
fuglue (fugu Glue) is a modern Project Management System based on HTTP. In addition to the access with web browser, it also supports WebDAV. The system is installed and operated as a web application on a web server (with Java Servlet support)
-
Host LLMs in Production With On-Demand GPUsDeploy your model, get an endpoint, pay only for compute time. No GPU provisioning or infrastructure management required.
-
10
gc-utils is a small set of scripts that let you import and update CVS repositories into git very easy and let you export patches back into a CVS working copy.
-
11
generic-auto-updater
A robust, user-friendly, clean and efficient Auto-Updater
After finishing a stable beta version of the "Auto-Updater" to be used by a specific company, I decided to duplicate the repository and making a few tweaks in the copy to turn it public (and generic) in order for it to be used by anyone. And thus, the first version of the "Generic Auto-Updater" was born! - A robust, user-friendly, clean and efficient Auto-Updater for anyone who wishes to maintain their client's users always updated based on some server directory. -
12
gennf is a distributed version management system with code signing support written in Common Lisp incorporating ideas from Meta-CVS.
-
13
ghooks
Simple git hooks
Simple git hooks. It is not advised to install ghooks as a production dependency, as it will install git hooks in your production environment as well. Please install it under the devDependencies section of your package.json. Please also note, that it is absolutely not advised to install ghooks globally. To work as expected, make it a development dependency of your project(s). Add a config.ghooks entry in your package.json and simply specify which git hooks you want and their corresponding commands. The hooks' working directory is relative to the git root (where you have your .git directory). This means that if your package.json is in a subdirectory of your git repository, you'll need to cd into the directory before running any npm scripts. -
14
git absorb
git commit --fixup, but automatic
This is a port of Facebook's hg absorb. Facebook demoed hg absorb which is probably the coolest workflow enhancement I've seen to version control in years. Essentially, when your working directory has uncommitted changes on top of draft changesets, you can run hg absorb and the uncommitted modifications are automagically folded ("absorbed") into the appropriate draft ancestor changesets. This is essentially doing hg histedit + "roll" actions without having to make a commit or manually make history modification rules. The command essentially looks at the lines that were modified, finds a changeset modifying those lines, and amends that changeset to include your uncommitted changes. If the changes can't be made without conflicts, they remain uncommitted. This workflow is insanely useful for things like applying review feedback. You just make file changes, run hg absorb and the mapping of changes to commits sorts itself out. It is magical. -
15
git push no-mistakes
git push no-mistakes
git push no-mistakes is a Git workflow tool that places a local validation gate in front of a real remote repository. Instead of pushing directly to origin, the user pushes to a no-mistakes remote. The tool creates a disposable worktree, runs an AI-driven validation pipeline, and only forwards the branch after every check passes. Its pipeline can review, test, check documentation, run linting, push the branch, open a pull request, watch CI, and apply safe automatic fixes. It supports coding agents such as Claude, Codex, Rovo Dev, OpenCode, Pi, and ACP-based targets through acpx. Overall, it helps developers create cleaner pull requests while keeping the human in control of approvals and judgment calls. -
16
git-auto-commit Action
Automatically Commit changed Files back to GitHub
Automatically Commit changed Files back to GitHub with GitHub Actions for the 80% use case. A GitHub Action to detect changed files during a Workflow run and to commit and push them back to the GitHub repository. By default, the commit is made in the name of "GitHub Actions" and co-authored by the user that made the last commit. Note that the Action has to be used in a Job that runs on a UNIX system (e.g. ubuntu-latest). If you don't use the default permission of the GITHUB_TOKEN, give the Job or Workflow at least the contents: write permission. The goal of this Action is to be "the Action for committing files for the 80% use case". Therefore, you might run into issues if your Workflow falls into the not supported 20% portion. If your Workflow can't push the commit to the repository because of authentication issues, please update your Workflow configuration. -
17
git-bug
Distributed, offline-first bug tracker embedded in git, with bridges
git-bug is fully embedded in git, you only need your git repository to have a bug tracker. git-bug is distributed. Use your normal git remote to collaborate, push and pull your bugs! git-bug works offline, in a plane or under the sea? Keep reading and writing bugs! It prevents vendor lock-in: your usual service is down or went bad? You already have a full backup. It is fast, listing bugs or opening them is a matter of milliseconds. git-bug doesn't pollute your project, no files are added in your project. git-bug integrates with your tooling, use the UI you like (CLI, terminal, web) or integrate with your existing tools through the CLI or the GraphQL API. git-bug bridges to other bug trackers. Use bridges to import and export to other trackers. An interactive terminal UI is available using the command git bug termui to browse and edit bugs. -
18
git-cal
github like contributions calendar on terminal
git-cal generates a terminal-friendly contribution calendar for your Git activity, echoing the familiar heatmap seen on hosting sites but rendered in plain text. It scans your repositories’ commit history and aggregates changes per day, then prints a compact grid that highlights streaks and quieter periods. The output works in standard shells, making it handy for dashboards, status emails, or a lightweight snapshot of productivity without opening a browser. Options typically let you choose time ranges, color intensity (where terminals support it), and which repositories to include. Because it reads local Git metadata, it respects your privacy and can include private work you don’t push to public remotes. For developers who like quick visual feedback in the CLI, git-cal turns raw commit timestamps into an at-a-glance activity portrait. -
19
git-chglog
CHANGELOG generator implemented in Go (Golang)
Package chglog implements the main logic for the CHANGELOG generate. git-chglog internally uses the git command to get data to include in the CHANGELOG. The basic steps are as follows. Get all the tags. Get the commits contained between tagA and tagB. Execute all tags corresponding to the tag query that was specified in Steps 1 and 2. The compiled docker images are maintained on quay.io. git-chglog requires configuration files and templates to generate a CHANGELOG. However, it is a waste of time to create configuration files and templates from scratch. Therefore we recommend using the --init option which will create them interactively. CHANGELOG style. Automatic linking of issues and notices, initial value setting such as merges etc. are done automatically. Metadata for CHANGELOG. Depending on Style, it is sometimes used in processing, so it is recommended to specify it. -
20
git-cola
git-cola: The highly caffeinated Git GUI
Git Cola is a sleek and powerful graphical user interface for Git. Git Cola is free software and written in Python (v2 + v3). Git Cola uses QtPy, so you can choose between PyQt6, PyQt5 and PySide2 by setting the QT_API environment variable to pyqt6, pyqt5 or pyside2 as desired. qtpy defaults to pyqt6 and falls back to pyqt6 and pyside2 if pyqt5 is not installed. Git Cola enables additional features when the following Python modules are installed. send2trash enables cross-platform "Send to Trash" functionality. Never run pip install or make install as root or outside of a Python virtualenv! If you don't have PyQt installed then the easiest way to get it is to use a Python virtualenv and install Git Cola into it in "editable" mode. This install method lets you upgrade Git Cola by running git pull. -
21
-
22
git-cz
Semantic Git commits
git-cz is a command-line tool designed to guide developers in writing structured, conventional commits. Rather than manually typing commit messages, this tool prompts you to select commit types, scopes, and write descriptions according to a defined format. It integrates with the popular commitizen ecosystem so that when you run npx git-cz or similar, you are prompted through a workflow instead of free-form message. The project emphasises consistency and readability in commit history, helping teams enforce semantic or conventional commit message formats. It supports custom configuration (for example via a changelog.config.js file) so you can adapt the prompts or types to your project’s conventions. Because it is open source (licensed under Unlicense) it can be freely integrated within CI pipelines or commit hooks to standardise message formats. -
23
git-delete-merged-branches
Command-line tool to delete merged Git branches
A convenient command-line tool helping you keep repositories clean. Supports deletion of both local and remote branches. Detects multiple forms of de-facto merges (rebase merges, squash merges (needs --effort=3), single or range cherry-picks… leveraging git cherry). Supports workflows with multiple release branches, e.g. only delete branches that have been merged to all of master, dev and staging. Quick interactive configuration. Provider agnostic: Works with GitHub, GitLab, Gitea and any other Git hosting. Takes safety seriously. Deletion is a sharp knife that requires care. While git reflog would have your back in most cases, git-delete-merged-branches takes safety seriously. git push is used with --force-with-lease so if the server and you have a different understanding of that branch, it is not deleted. There is no use of os.system or shell code to go wrong. -
24
git-imerge
Incremental merge for git
Perform a merge between two branches incrementally. If conflicts are encountered, figure out exactly which pairs of commits conflict, and present the user with one pairwise conflict at a time for resolution. Reduce the pain of resolving merge conflicts to its unavoidable minimum, by finding and presenting the smallest possible conflicts: those between the changes introduced by one commit from each branch. Allow a merge to be saved, tested, interrupted, published, and collaborated on while it is in progress. Multiple incremental merges can be in progress at the same time. Each incremental merge has a name, and its progress is recorded in the Git repository as references under refs/imerge/NAME. The current state of an incremental merge can be visualized using the diagram command. An incremental merge can be interrupted and resumed arbitrarily, or even pushed to a server to allow somebody else to work on it. -
25
git-messenger.vim
Vim and Neovim plugin to reveal the commit messages
git-messenger.vim is a Vim and Neovim plugin that quickly reveals the Git commit message behind the line under the cursor. It helps developers understand why a line was added or changed without leaving the editor. The plugin shows the latest related commit in a popup window, floating window, or preview window depending on the editor version. If the most recent commit is not enough, users can explore older commits from the same interface. It can also show the diff for a selected commit, including options for unified and word diffs. This makes it useful when reading unfamiliar code, reviewing history, or debugging changes with context from version control.
