Open Source Git Software - Page 3
Sort By:
Git Software
View 80 business solutions-
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.
-
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.
-
1
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)! -
2
Magit
A Git porcelain inside Emacs
Magit is a complete text-based user interface to Git. It fills the glaring gap between the Git command-line interface and various GUIs, letting you perform trivial as well as elaborate version control tasks with just a couple of mnemonic key presses. Magit looks like a prettified version of what you get after running a few Git commands but in Magit every bit of visible information is also actionable to an extent that goes far beyond what any Git GUI provides and it takes care of automatically refreshing this output when it becomes outdated. In the background Magit just runs Git commands and if you wish you can see what exactly is being run, making it possible for you to learn the git command-line by using Magit. Using Magit for a while will make you a more effective version control user. Magit supports and streamlines the use of Git features that most users and developers of other Git clients apparently thought could not be reasonably mapped to a non-command-line interface. -
3
Netlify CMS
A Git-based CMS for static site generators
Open source content management for your Git workflow. Use Netlify CMS with any static site generator for a faster and more flexible web project. Get the speed, security, and scalability of a static site, while still providing a convenient editing interface for content. Content is stored in your Git repository alongside your code for easier versioning, multi-channel publishing, and the option to handle content updates directly in Git. Netlify CMS is built as a single-page React app. Create custom-styled previews, UI widgets, and editor plugins or add backends to support different Git platform APIs. Getting started is simple and free. Choose a template that’s pre-configured with a static site generator and deploys to a global CDN in one click. You get to implement modern front end tools to deliver a faster, safer, and more scalable site. Editors get a friendly UI and intuitive workflow that meets their content management requirements. -
4
Onefetch
Git repository summary on your terminal
Onefetch is a command-line Git information tool written in Rust that displays project information and code statistics for a local Git repository directly on your terminal. The tool is completely offline, no network access is required. By default, the repo's information is displayed alongside the dominant language's logo, but you can further configure onefetch to instead use an image, on supported terminals, text input, or nothing at all. It automatically detects open source licenses from texts and provides the user with valuable information like code distribution, pending changes, number of dependencies (by package manager), top contributors (by number of commits), the size on disk, creation date, LOC (lines of code), etc. Onefetch can be configured via command-line flags to display exactly what you want, the way you want it to: you can customize ASCII/Text formatting, disable info lines, ignore files & directories, and output in multiple formats (JSON, Yaml), etc. -
99.99% Uptime for MySQL and PostgreSQL DatabasesCloud SQL Enterprise Plus delivers near-zero downtime with 35 days of point-in-time recovery. Supports MySQL, PostgreSQL, and SQL Server.
-
5
SwiftPamphletApp
SwiftUI + Combine + Swift Concurrency Aysnc/Await Actor + GitHub API
Dai Ming's development brochure, a living development manual. macOS app developed with SwiftUI + Combine + Swift Concurrency Aysnc/Await Actor + GitHub API. Pull the code. Directly compile and generate a manual program without Github function. If you want to use the Github function, you can add your GitHub Access Token to gitHubAccessToken in SwiftPamphletAppConfig.swift. Get the GitHub Access Token at Personal Access Tokens here. Remember to tick repo and user in scope. Both Xcode and macOS need to be upgraded to the latest version. You can use compile.command to compile the manual program, no need to open Xcode to set up a personal development account, just add your GitHub Access Token to gitHubAccessToken in SwiftPamphletAppConfig.swift , and then click compile.command twice to wait for the job to complete. The booklet can easily view the Swift syntax, and there are some guides for the use of the main libraries. The content is still being improved. -
6
actions/github-script
Write workflows scripting the GitHub API in JavaScript
This action makes it easy to quickly write a script in your workflow that uses the GitHub API and the workflow run context. To use this action, provide an input named script that contains the body of an asynchronous function call. Since the script is just a function body, these values will already be defined, so you don't have to import them. All scripts are now run with Node 16 instead of Node 12 and are affected by any breaking changes between Node 12 and 16. By default, the JSON-encoded return value of the function is set as the "result" in the output of a github-script step. For some workflows, string encoding is preferred. This option can be set using the result-encoding input. By default, requests made with the github instance will not be retried. You can configure this with the retries option. -
7
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. -
8
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. -
9
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. -
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.
-
10
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. -
11
git-flow-next
Git extensions to provide high-level repository operations
git-flow-next is a branching model and a set of command-line extensions tailored to enforce that branching model for Git repositories. The underlying workflow was first described in 2010 and is designed around two long-lived branches (master (or main) for production-ready code, and develop for integration) and multiple supporting short-lived branches (feature, release, hotfix) for day-to-day development. With git-flow, each type of branch has explicit purpose and merge rules: features merge back into develop, release branches prepare towards master, and hotfixes branch off master for urgent repairs. The repository you referenced provides the actual shell scripts (and wrappers) implementing sub‐commands like git flow feature start, git flow release finish, etc., making the workflow operational rather than purely conceptual. -
12
joe
A .gitignore magician in your command line
A .gitignore magician in your command line. Joe generates .gitignore files from the command line for you. After install, make sure to run joe u. This will download all .gitignore files in ~/joe-data/ folder. Download the latest binary from the Releases page. It's the easiest way to get started with joe. Make sure to add the location of the binary to your $PATH. You can also use joe to append to a global .gitignore. These can be helpful when you want to ignore files generated by an IDE, OS, or otherwise. Joe isn't just a generator for .gitignore files. You can use it and its output wherever a SCM is used. -
13
Branchless workflow for Git
High-velocity, monorepo-scale workflow for Git
git-branchless is a suite of tools that enhances Git in several ways. It makes Git easier to use, both for novices and for power users. Patch-stack workflows: strong support for "patch-stack" workflows as used by the Linux and Git projects, as well as at many large tech companies. (This is how Git was "meant" to be used.) Prototyping and experimenting workflows: strong support for prototyping and experimental work via "divergent" development. git sync: to rebase all local commit stacks and branches without having to check them out first. git move: The ability to move subtrees rather than "sticks" while cleaning up old branches, not touching the working copy, etc. Anonymous branching: reduces the overhead of branching for experimental work. In-memory operations: to modify the commit graph without having to check out the commits in question. git next/prev: to quickly jump between commits and branches in a commit stack. -
14
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. -
15
Git Extras
GIT utilities, repo summary, repl, changelog population, and more
GIT extra utilities, like repo summary, repl, changelog population, author commit percentages and more. Supports several sub-commands such as git-ignore, git-setup, git-summary, git-changelog, git-effort, etc. Some commands require extra dependencies which are unavailable in some platforms. You may need to install them manually. Note that only the Homebrew package is maintained by the git-extras developers directly. Other packages are maintained by the distribution's packagers or third-party volunteers. Installing from Homebrew will not give you the option omit certain git-extras if they conflict with existing git aliases. To have this option, build from source. -
16
GitBucket
A Git platform powered by Scala
A Git platform powered by Scala with easy installation, high extensibility & GitHub API compatibility. GitBucket is a Git web platform powered by Scala offering, easy installation, intuitive UI, high extensibility by plugins, API compatibility with GitHub. You can also deploy gitbucket.war to a servlet container which supports Servlet 3.0 (like Jetty, Tomcat, JBoss, etc). To upgrade GitBucket, replace gitbucket.war with the new version, after stopping GitBucket. All GitBucket data is stored in HOME/.gitbucket by default. So if you want to back up GitBucket's data, copy the directory to the backup location. If you want to try the development version of GitBucket, or want to contribute to the project, please see the Developer's Guide. It provides instructions on building from source and on setting up an IDE for debugging. It also contains documentation of the core concepts used within the project. -
17
GitHub Pages Deploy Action
Automatically deploy your project to GitHub Pages using GitHub Actions
Automatically deploy your project to GitHub Pages using GitHub Actions. This action can be configured to push your production-ready code into any branch you'd like. You can include the action in your workflow to trigger any event that GitHub actions supports. If the remote branch that you wish to deploy to doesn't already exist the action will create it for you. Your workflow will also need to include the actions/checkout step before this workflow runs in order for the deployment to work. If you intend to make multiple deployments in quick succession you may need to leverage the concurrency parameter in your workflow to prevent overlaps. The with portion of the workflow must be configured before the action will work. You can add these in the with section found in the examples above. Any secrets must be referenced using the bracket syntax and stored in the GitHub repository's Settings/Secrets menu. -
18
Gitblit
pure java git solution
Gitblit is an open-source, pure Java stack for managing, viewing, and serving Git repositories. It's designed primarily as a tool for small workgroups who want to host centralized repositories. Gitblit GO is an integrated, single-stack solution based on Jetty. You do not need Apache httpd, Perl, Git, or Gitweb. Should you want to use some or all of those, you still can; Gitblit plays nice with the other kids on the block. This is what you should download if you want to go from zero to Git in less than 5 mins. Gitblit WAR is what you should download if you already have a servlet container available that you wish to use. Jetty 6/7/8 and Tomcat 6/7 are known to work. Generally, any Servlet 2.5 or Servlet 3.0 container should work. Gitblit can be used as a dumb repository viewer with no administrative controls or user accounts. Gitblit can be used as a complete Git stack for cloning, pushing, and repository access control. -
19
Gradle Git Version
A Gradle plugin that uses `git describe` to produce a version string
This Gradle plugin derives your project’s version directly from the state of the Git repository, turning tags and commits into consistent semantic versions. It reads the most recent tag, the number of commits since that tag, and whether the working tree is dirty, then composes a deterministic version string. Teams can enforce patterns (for example, treating non-tagged builds as snapshots) and keep CI builds reproducible without hardcoding versions in build.gradle. The plugin integrates with Gradle’s project.version, so the computed version flows automatically into publishing, packaging, and artifact naming. It works well in branching workflows by incorporating branch or distance information, making debug artifacts easy to trace back to source. By centralizing version logic around Git history, it eliminates manual bumps and reduces mistakes when cutting releases across multiple modules. -
20
Grgit
The Groovy way to use Git
Grgit is a Groovy‑friendly wrapper around Eclipse JGit that simplifies Git operations within Groovy scripts or Gradle builds. It provides a cleaner, fluent API for common Git tasks (clone, commit, tag, branch), and ships as a Gradle plugin for easy project integration. -
21
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. -
22
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. -
23
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. -
24
git-sketch-plugin
A Git client generating pretty diffs built right into Sketch
A Git client generating pretty diffs built right into Sketch. A Git client built right into Sketch. The plugin really improves the review process by exporting an image for every part of the design. Every member of the team can quickly see what the next iteration will change through Github’s interface. Each step of the design process is now documented. Newcomers are able to understand how we ended up with the current iteration and why we went with some options and not others. Create a new branch when you start working on a new feature. Work normally on your design. Save the file. Commit the changes with a meaningful message describing them. The plugin will extract the artboards in your file in order to show the differences easily. Push your changes to the remote. Create a pull request from your branch to the master branch. Voila. Your co-workers can review the changes, comment on them and approve them. Once approved, merge the pull request. -
25
gitoxide
An idiomatic, lean, fast & safe pure Rust implementation of Git
An idiomatic, lean, fast & safe pure Rust implementation of Git. gix is a command-line interface (CLI) to access git repositories. It's written to optimize the user experience and perform as well or better than the canonical implementation. Furthermore, it provides an easy and safe to use API in the form of various small crates for implementing your own tools in a breeze. Please see 'Development Status' for a listing of all crates and their capabilities. Please note that all functionality comes from the gitoxide-core library, which mirrors these capabilities and itself relies on all git-* crates. Limit the number of threads used in operations that support it. Choose between 'human' and 'JSON' output formats. Display general information about the index itself, with detailed extension information by default and detailed information about the TREE extension. Follow the linked crate name for detailed status.
