Open Source Git Software - Page 2
Sort By:
Git Software
View 82 business solutions-
Custom VMs From 1 to 96 vCPUs With 99.95% UptimeLive migration and automatic failover keep workloads online through maintenance. One free e2-micro VM every month.
-
Cut Data Warehouse Costs by 54%BigQuery delivers 54% lower TCO with exabyte scale and flexible pricing. Free migration tools handle the SQL translation automatically.
-
1
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. -
2
ohmyposh.dev
A prompt theme engine for any shell
Oh My Posh enables you to use the full-color set of your terminal by using colors to define and render the prompt. Easily adjust existing themes or create your own. From standard segments all the way to custom implementations. No matter which shell you're using, or even how many, you can carry the configuration from one shell and/or machine to another for the same prompt everywhere you work. What started as the offspring of oh-my-posh2 for PowerShell resulted in a cross platform, highly customizable and extensible prompt theme engine. After 4 years of working on oh-my-posh, a modern and more efficient tool was needed to suit my personal needs. When you look at prompts like Agnoster or Paradox, you notice they usually consist of a few building blocks which contain one or more segments that display some sort of information. The configuration of Oh My Posh works exactly like that. Blocks are a combination of one or more segments. -
3
Dolt
Dolt, it's Git for data
Dolt is a SQL database that you can fork, clone, branch, merge, push and pull just like a git repository. Connect to Dolt just like any MySQL database to run queries or update the data using SQL commands. Use the command line interface to import CSV files, commit your changes, push them to a remote, or merge your teammate's changes. All the commands you know for Git work exactly the same for Dolt. Git versions files, Dolt versions tables. It's like Git and MySQL had a baby. We also built DoltHub, a place to share Dolt databases. We host public data for free. If you want to host your own version of DoltHub, we have DoltLab. If you want us to run a Dolt server for you, we have Hosted Dolt. MySQL comes with a MySQL server called mysqld and a MySQL client called mysql. You're only interested in the client. After following the instructions from MySQL's documentation, make sure you have a copy of the mysql client on your path. -
4
jupyterlab-git
A Git extension for JupyterLab
A JupyterLab extension for version control using Git. To see the extension in action, open the example notebook included in the Binder demo. Open the Git extension from the Git tab on the left panel. This extension tries to handle credentials for HTTP(S) connections (if you don't have set up a credential manager). But not for other SSH connections. The extension can cache temporarily (by default for an hour) credentials. To use the caching, you will need to check the option Save my login temporarily in the dialog asking your credentials. Once installed, extension behavior can be modified via the following settings which can be set in JupyterLab's advanced settings editor. Set post git init actions. It is possible to provide a list of commands to be executed in a folder after it is initialized as Git repository. Set path patterns to exclude from this extension. You can use wildcard and interrogation mark for respectively everything or any single character in the pattern. -
Fully Managed MySQL, PostgreSQL, and SQL ServerCloud SQL handles your database ops end to end, so you can focus on your app.
-
5
Git Large File Storage
Git extension for versioning large files
An open source Git extension for versioning large files. Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise. Download and install the Git command line extension. Once downloaded and installed, set up Git LFS for your user account. In each Git repository where you want to use Git LFS, select the file types you'd like Git LFS to manage (or directly edit your .gitattributes). You can configure additional file extensions at any time. Host more in your Git repositories. External file storage makes it easy to keep your repository at a manageable size. Download less data. This means faster cloning and fetching from repositories that deal with large files. Work like you always do on Git, no need for additional commands, secondary storage systems, or toolsets. -
6
Jujutsu
A Git-compatible DVCS that is both simple and powerful
Jujutsu (JJ VCS) is a modern, Git-compatible version control system designed to simplify and improve how developers manage code changes. It offers a clean and intuitive workflow that works well for both individual developers and large teams with complex histories. Jujutsu separates its user interface from its storage backend, allowing it to use Git repositories while rethinking the developer experience. The system treats the working copy as a real commit, removing the need for staging areas or stashes. Jujutsu records conflicts as first-class objects, making conflict resolution more flexible and reliable. It also maintains a complete operation log, allowing users to undo almost any action. Jujutsu aims to deliver powerful history rewriting and rebasing features without the complexity commonly associated with traditional tools. -
7
PyGitHub
Typed interactions with the GitHub API v3
PyGitHub is a Python library to access the GitHub REST API. This library enables you to manage GitHub resources such as repositories, user profiles, and organizations in your Python applications. PyGithub is a Python library to use the Github API v3. With it, you can manage your Github resources (repositories, user profiles, organizations, etc.) from Python scripts. Should you have any question, any remark, or if you find a bug, or if there is something you can do with the API but not with PyGithub, please open an issue. -
8
git-tfs
A Git/TFS bridge, similar to git-svn
git-tfs is a two-way bridge between TFS (Team Foundation Server) and git, similar to git-svn. It fetches TFS commits into a git repository, and lets you push your updates back to TFS. git-tfs is a two-way bridge between TFS and git, similar to git-svn. If the build fails to build some GitTfs.Vs201x projects, just unload in Visual Studio all the projects you are not interested in to be able to build and use your own version. You could also install, the Team Foundation Server Object Model for Tfs 2012 (chocolatey) and Tfs 2013 (chocolatey). -
9
PicX
GitHub API
An image bed management tool with CDN acceleration function developed based on GitHub API. No need to download and install, use it online on the web page! free! Stablize! Convenient! Extremely fast! Writing articles with static blogs such as Hexo, VuePress, Hugo, etc., I don’t know where to save the pictures. Deliberately spending money to rent a cloud server to host pictures, it is too expensive and not worth it, and the upload configuration is cumbersome. The link to the favorite picture copied from the Internet will become invalid one day after using it. Using other paid image beds, the speed is slow, the capacity is small, and the time and flow are limited. Looking for a picture bed that is really free, stable, unlimited in capacity, and fast in access speed. So, come and try the PicX picture bed , it is specially made for technical bloggers, whoever uses it will know. Support one- click copying of external links of pictures and one- click conversion of Markdown format. -
$300 Free Credits to Build on Google CloudPut your $300 in credit toward real workloads, then keep building with free monthly usage for 20+ products. No commitment and no charge until you upgrade.
-
10
Blamer.el
A git blame plugin for emacs inspired by VS Code's GitLens plugin
A git blame plugin for emacs inspired by VS Code’s GitLens plugin and Vim plugin. -
11
Checkout v7
Action for checking out a repo
Checkout v7 is the official GitHub Action for checking out repository code inside a GitHub Actions workflow. It places the selected repository under the workflow workspace so build, test, lint, release, or deployment steps can access the files. By default, it fetches only one commit for the ref or SHA that triggered the workflow, but it can also fetch full branch and tag history. The action supports checking out different repositories, private repositories, pull request commits, submodules, Git LFS files, sparse paths, and custom paths. It can use Git credentials, SSH keys, safe directory configuration, and GitHub Enterprise Server URLs. Recent versions also focus on stronger credential handling and safer behavior around fork pull request code in trusted workflow contexts. -
12
Guitar
Git GUI Client
Many Git client apps have some problems. It's too late to start up, falls well, is user registration tedious when downloading, is paid for commercial use, is not multi-platform, or is an animation or visual effect. It was said that the production was overkill and the wizard and the source code were not published. I tried to eliminate such inconvenience as much as possible. At first I started developing it for my own study, because I was interested in learning how to use Git and how it worked inside. Some of the best engineers of the time may think Git in GUI. That's a lot of it. When I want to execute a command that I rarely use, I sometimes force myself to do not rely on the GUI, open the terminal and hand enter the git command. If you find a feature that you find useful, you can incorporate it into this app. You can use it comfortably for daily use of Git operations, want to see the commit graphs cleanly, or just for such uses. -
13
Husky
Git hooks made easy
Husky is a tool that makes handling Git hooks a lot easier, and lets you run the scripts you want at those stages. It works by including an object right within your package.json file. This then configures Husky so that it runs the scripts you specify. After that, it's Husky's responsibility to manage at which point in the Git lifecycle your scripts will run. Husky helps to improve your commits, lets you run tests, lint code and more when you commit or push. It is very lightweight, with zero dependencies and is capable of supporting all Git hooks. -
14
Kactus
A true version control tool for designers
Introducing true design version control without changing your tools. Manage changes, document work and keep your team in sync. Enjoy all the benefits of git with our simple UI, leaving you more time to focus on what matters — your design. Create branches, collaborate with other designers or developers, and commit changes without touching the command line. Every pixel is completely open source. Build the features you need and become a part of future Kactus releases. It brings the entire git flow to sketch: branches, pull requests, team collaboration (you can work on the same file and automatically merge the changes), etc. You can share pages across multiple sketch files. You can publish pages on the internet and import them in another project (soon)! -
15
commitlint
Lint commit messages
commitlint checks if your commit messages meet the conventional commit format. commitlint helps your team adhere to a commit convention. By supporting npm-installed configurations it makes sharing of commit conventions easy. We're not a sponsored OSS project. Therefore we can't promise that we will release patch versions for older releases in a timely manner. If you are stuck on an older version and need a security patch we're happy if you can provide a PR. If something in between fails (like a new packages was added and needs to be published for the first time but you forgot) you can use lerna publish from-package to publish anythign that has not been published yet. We identify ease of adoption and developer experience as fields where there is room and need for improvement. The items on the roadmap should enhance commitlint regarding those aspects. -
16
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. -
17
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. -
18
git-toolbelt
A suite of useful Git commands that aid with scripting
git-toolbelt is a collection of practical Git helper commands for daily command-line work and scripting. It adds small utilities that simplify common repository tasks that are possible with Git but annoying to type repeatedly. The project includes commands for creating WIP savepoint commits, listing modified files, updating many repositories, and inspecting local or remote branch state. It is designed for developers who already use Git heavily and want a faster workflow around repetitive operations. The tools are intentionally lightweight and shell-friendly, so they fit naturally into terminal aliases, scripts, and editor integrations. Its main value is turning frequent Git chores into short, readable commands. -
19
gitsigns.nvim
Git integration for buffers
Super fast git decorations implemented purely in lua/teal. Signs for added, removed, and changed lines. Asynchronous using luv. Navigation between hunks. Stage hunks (with undo). Preview diffs of hunks (with word diff). Customizable (signs, highlights, mappings, etc). Status bar integration. Git blame a specific line using virtual text. Hunk text object. Automatically follow files moved in the index. Live intra-line word diff. Ability to display deleted/changed lines via virtual lines. Support for yadm. Support for detached working trees. If you are running a development version of Neovim (aka master), then breakage may occur if your build is behind latest. Gitsigns provides an on_attach callback which can be used to setup buffer mappings. This plugin is actively developed and by one of the most well regarded vim plugin developers. Gitsigns will only implement features of this plugin if: it is simple, or, the technologies leveraged by Gitsigns (LuaJIT, Libuv, Neovim's API, etc). -
20
opam
opam is a source-based package manager
Opam is a source-based package manager for OCaml. It supports multiple simultaneous compiler installations, flexible package constraints, and a Git-friendly development workflow. Opam was created and is maintained by OCamlPro. To get started, checkout the Install and Usage guides. Run ./configure. If you don't have the dependencies installed, this will locally take care of all OCaml dependencies for you (downloading them, unless you used the inclusive archive we provide for each release). This is all you need for installing and using opam, but if you want to use the opam-lib (to work on opam-related tools), you need to link it to installed libraries. It's easier to already have a working opam installation in this case, so you can do it as a second step. If you install on your system (without changing the prefix), you will need to install as root (sudo). As sudo do not propagate environment variables, there wil be some errors. -
21
posh-git
A PowerShell environment for Git
posh-git is a PowerShell module which provides Git/PowerShell integration. The prompt within Git repositories can show the current branch and the state of files (additions, modifications, deletions) within. Provides tab completion for common commands when using git. Prompt formatting, among other things, can be customized. Displaying file status in the git prompt for a very large repo can be prohibitively slow. Rather than turn off file status entirely, you can disable it on a repo-by-repo basis by adding individual repository paths. PowerShell generates its prompt by executing a prompt function, if one exists. posh-git defines such a function in profile.example.ps1 that outputs the current working directory followed by an abbreviated git status. -
22
CPM.cmake
CMake's missing package manager
CPM.cmake is a cross-platform CMake script that adds dependency management capabilities to CMake. It's built as a thin wrapper around CMake's FetchContent module that adds version control, caching, a simple API and more. Any downloadable project or resource can be added as a version-controlled dependency though CPM, it is not necessary to modify or package anything. Projects using modern CMake are automatically configured and their targets can be used immediately. For everything else, the targets can be created manually after the dependency has been downloaded. After CPM.cmake has been added to your project, the function CPMAddPackage can be used to fetch and configure a dependency. Afterwards, any targets defined in the dependency can be used directly. CPMAddPackage takes the following named parameters. The origin may be specified by a GIT_REPOSITORY, but other sources, such as direct URLs, are also supported. -
23
Commitizen for contributors
The commitizen command line utility
When you commit with Commitizen, you'll be prompted to fill out any required commit fields at commit time. No more waiting until later for a git commit hook to run and reject your commit (though that can still be helpful). No more digging through CONTRIBUTING.md to find what the preferred format is. Get instant feedback on your commit message formatting and be prompted for required fields. Commitizen is currently tested against Node.js 12, 14, & 16, although it may work in older versions of Node.js. You should also have npm 6 or greater. When you're working in a Commitizen-friendly repository, you'll be prompted to fill in any required fields, and your commit messages will be formatted according to the standards defined by project maintainers. Installing and running Commitizen locally allows you to make sure that developers are running the exact same version of Commitizen on every machine. -
24
NodeGit
Native Node bindings to Git
Asynchronous native Node bindings to libgit2. NodeGit will work on most systems out-of-the-box without any native dependencies. If you receive errors about libstdc++, which are commonly experienced when building on Travis-CI, you can fix this by upgrading to the latest libstdc++-4.9. If you wish to help contribute to NodeGit it is useful to build locally. If you encounter errors, you most likely have not configured the dependencies correctly. You will need libpcre, libpcreposix, libkrb5, libk5crypto, and libcom_err libraries installed on your Linux machine. When building locally, you will also need development packages for kerberos and pcre, so both pcre-config, and krb5-config utilities must be present on your machine. -
25
Talisman
Talisman validates the outgoing changeset
Talisman is a tool that installs a hook to your repository to ensure that potential secrets or sensitive information do not leave the developer's workstation. It validates the outgoing changeset for things that look suspicious - such as potential SSH keys, authorization tokens, private keys etc. Talisman can also be used as a repository history scanner to detect secrets that have already been checked in, so that you can take an informed decision to safeguard secrets. We recommend installing Talisman as a pre-commit git hook template, as that will cause Talisman to be present, not only in your existing git repositories, but also in any new repository that you 'init' or 'clone'. Installation of Talisman globally does not clobber pre-existing hooks on repositories. If the installation script finds any existing hooks, it will only indicate so on the console. After the installation is successful, Talisman will run checks for obvious secrets automatically before each commit or push.
