Open Source Git Software - Page 4
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.
-
Build Agents and Models on One PlatformGemini Enterprise Agent Platform is Google Cloud's comprehensive platform for developers to build, scale, govern, and optimize agents and models. Choose from Google's most advanced models and third-party models like Anthropic's Claude Model Family.
-
1
Git Interactive Rebase Tool
Native cross-platform full feature terminal-based sequence editor
Native cross-platform full feature terminal-based sequence editor for interactive rebase in Git 1.7.8+. Built and works on Linux, macOS, Windows and many others. Easily set the action to pick, squash, fixup, edit, reword and drop. Reorder the action list with a single key press. Change action and reorder multiple lines at once with visual mode. View the commit overview, and a full commit diff with a press of a key. Easily edit the command that is run by an exec command. Need to do something in your Git editor? Quickly shell out to your editor, make a change and return to the tool. GitBash requires the use of winpty in order to work correctly. The tool has built-in help that can be accessed by using the ? key. Key bindings can be customized, see configuration for all key bindings and information on configuring. -
2
Git-FTP
Uses Git to upload only changed files to FTP servers
If you use Git and you need to upload your files to an FTP server, Git-ftp can save you some time and bandwidth by uploading only those files that changed since the last upload. It keeps track of the uploaded files by storing the commit id in a log file on the server. It uses Git to determine which local files have changed. You can easily deploy another branch or go back in the Git history to upload an older version. git-ftp was not designed as centralized deployment tool. While a commit is being pushed and uploaded to the FTP server, all files belonging to that revision must remain untouched until git-ftp has successfully finished the upload. Otherwise, the contents of the uploaded file will not match the contents of the file referenced in the commit. -
3
Tig
Text-mode interface for git
Tig is an ncurses-based text-mode interface for git. It functions mainly as a Git repository browser, but can also assist in staging changes for commit at chunk level and act as a pager for output from various Git commands. Tig allows you to browse changes in a Git repository and can additionally act as a pager for output of various Git commands. When used as a pager, it will display input from stdin and colorize it. When browsing repositories, Tig uses the underlying Git commands to present the user with various views, such as summarized commit log and showing the commit with the log message, diffstat, and the diff. If stdin is a pipe, any log or diff options will be ignored and the pager view will be opened loading data from stdin. The pager mode can be used for colorizing output from various Git commands. All Git command options specified on the command line will be passed to the given command and all will be shell quoted before they are passed to the shell. -
4
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. -
Go from Code to Production URL in SecondsSkip the Kubernetes configs. Cloud Run handles HTTPS, scaling, and infrastructure automatically. Two million requests free per month.
-
5
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. -
6
gitwatch
Watch a file or folder and automatically commit changes to a git repo
A bash script to watch a file or folder and commit changes to a git repo. Some programs auto-write their config files, without waiting for you to click an 'Apply' button; or even if there is such a button, most programs offer you no way of going back to an earlier version of your settings. If you commit your config file(s) to a git repo, you can track changes and go back to older versions. This script makes it convenient, to have all changes recorded automatically. If you use an editor that does not have built-in git support (or maybe if you don't like the git support it has), you can use gitwatch to automatically commit your files when you save them, or combine it with the editor's auto-save feature to fully automatically and regularly track your changes. If you have any other uses, or can think of ones, please let us know, and we can add them to this list! gitwatch can be installed from source by simply cloning the repository and putting the shell script into your $PATH. -
7
Conventional Changelog
Generate changelogs and release notes from a project's commit messages
The conventional-changelog repo is managed as a monorepo; it's composed of many npm packages. It's recommended you use the high-level standard-version library, which is a drop-in replacement for npm's version command, handling automated version bumping, tagging, and CHANGELOG generation. Alternatively, if you'd like to move towards completely automating your release process as an output from CI/CD, consider using semantic-release. We specifically limit our support to LTS versions of Node, not because this package won't work on other versions, but because we have a limited amount of time, and supporting LTS offers the greatest return on that investment. It's possible this package will work correctly on newer versions of Node. It may even be possible to use this package on older versions of Node, though that's more unlikely as we'll make every effort to take advantage of features available in the oldest LTS version we support. -
8
Fast git handover with mob
Tool for smooth git handover
Fast git handover for remote pair/mob programming. Switch to a separate branch with mob start and handover to the next person with mob next. Repeat. When you're done, get your changes into the staging area of the main branch with mob done and commit them. The perfect git handover is quick, requires no talking, and allows the rest of the team to continue discussing how to best solve the current problem undisturbed by the handover. mob is a thin wrapper around git. mob provides only a few environment variables for configuration. mob only uses the Go standard library and no 3rd party plugins. mob provides a copy'n'paste solution if it encounters an error. mob requires the user to do changes in non-wip branches. mob owns its wip branches. It will create wip branches, make commits, push them, but also delete them. -
9
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. -
Demo Series - Small Business Backup By VeeamWatch this on-demand demo series and learn how to protect your Microsoft 365 data with clear, simple, actionable steps that are easy to implement for businesses of all sizes.
-
10
GitButler
The GitButler version control client, backed by Git
GitButler is a modern Git-based version control client that pairs a graphical desktop experience with a complementary command-line tool, aiming to make everyday change management easier than traditional Git workflows. It keeps Git compatibility at the core, meaning your work still maps to commits, branches, and pushes to standard Git servers, but it rethinks how you interact with that underlying model. The project is designed around developer productivity, emphasizing smoother workflows for handling multiple streams of work, reviewing changes, and recovering from mistakes without the usual friction. It also positions itself for AI-assisted development patterns, where tooling needs to support rapid iteration and parallel work while staying understandable and reversible. By offering both GUI and CLI surfaces, it can fit into different team preferences, from visual-first change review to scriptable automation. -
11
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. -
12
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. -
13
Znap!
Znap! Fast, easy-to-use tools for Zsh dotfiles & plugins
Znap is a fast, light-weight set of tools to ease the use of Zsh plugins & Git repos and reduce your shell's startup time. Using Znap to manage your plugins can be as simple as putting this in your .zshrc file. Additionally, Znap makes it so that you actually need to have less in your .zshrc file, by automating several tasks for you. Note that the above example does not include any call to complist, compinit, or bashcompinit in the .zshrc file. That is because Znap will run these for you as needed. Znap compiles your scripts and functions in the background. This way, your shell will start up even faster next time! Znap automatically regenerates your comp dump file whenever you install or update a repo or change your .zshrc file. When using git 2.31.0 or newer, Znap automatically enables git maintenance in each repo that it manages. This automatically optimizes your repos in the background, so that your git and znap commands will run faster. -
14
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. -
15
git-recall
An interactive way to peruse your git history from the terminal
An interactive way to peruse your git history from the terminal. git-recall is a simple tool that allows you to easily go through your commits and check what you or other contributors in your team did. It doesn't aim to be a replacement for the git log command, but just to be a convenient way to recall what you've done from your terminal. You can install it by simply copying the git-recall script into any existing path (e.g. /usr/local/bin) or create your own directory and add it to the PATH variable. Once the commits are displayed, you can use either the arrow keys or j/k to switch between commits, press TAB or e to expand/reduce the commit's diff or q to quit. -
16
git-reflow
Reflow automatically creates pull requests
Reflow automatically creates pull requests, ensures the code review is approved, and squash merges finished branches to master with a great commit message template. Enforce code reviews across your team. Know that your entire team delivers code the same way. Reduce the knowledge needed to deliver great code. Have a commit history that's clean and actually usable. Revert features with ease (if needed). Work with diverse teams with less worry about different processes. Stop searching for other git workflows. Reflow covers 90% of your needs without junk you'll never use. Git-reflow's default process isn't meant to fit every team, which is why we've introduced Custom Workflows. With a custom workflow, you can add hooks to be run before, or after any command. Use one of our pre-configured workflows as a basis for your own. -
17
nbstripout
strip output from Jupyter and IPython notebooks
Opens a notebook, strips its output, and writes the outputless version to the original file. Useful mainly as a git filter or pre-commit hook for users who don't want to track output in VCS. This does mostly the same thing as the Clear All Output command in the notebook UI. You can download and install the latest version of nbstripout from PyPI, the Python package index. Strip output from IPython / Jupyter / Zeppelin notebook (modifies the file in-place). Usually, nbstripout is installed per repository so you can choose where to use it or not. You can choose to set the attributes in .gitattributes and commit this file to your repository, however there is no way to have git set up the filters automatically when someone clones a repository. This is by design, to prevent you from executing arbitrary and potentially malicious code when cloning a repository. -
18
Git Graph extension for VSC
View a Git Graph of your repository in Visual Studio Code
View a Git Graph of your repository, and easily perform Git actions from the graph. Configurable to look the way you want! View annotated tag details (name, email, date and message) Copy commit hashes, and branch, stash & tag names to the clipboard. View commit details and file changes by clicking on a commit. View the Visual Studio Code Diff of any file change by clicking on it. Open the current version of any file that was affected in the commit. Copy the path of any file that was affected in the commit to the clipboard. Click on any HTTP/HTTPS url in the commit body to open it in your default web browser. Compare any two commits by clicking on a commit, and then CTRL/CMD clicking on another commit. View the Visual Studio Code Diff of any file change between the selected commits by clicking on it. Open the current version of any file that was affected between the selected commits. -
19
Gitlogue
A cinematic Git commit replay tool for the terminal
Gitlogue provides a fun and creative command-line tool that turns your Git commit history into an animated replay, displaying your commits as if someone were typing the changes in real time with cinematic flair. When you run this tool in the terminal, it visually replays diffs line by line, highlights syntax, and shows changes evolving in a way that feels like watching a code story unfold, which can be entertaining and useful for reviewing history or showcasing progress. It builds on typical Git data but reshapes it into a compelling narrative with visual appeal, making it great for demos, teaching, or just savoring your development journey. The tool is standalone and designed to be easy to install and run, so users don’t need complex setups to enjoy animated commit histories. Gitlogue adds atmosphere and personality to otherwise dry version control logs, and it supports terminal-friendly output that respects your existing workflow. -
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
Monkey for GitHub
Monkey is an unofficial GitHub client for iOS
Monkey is an unofficial GitHub client. Monkey for GitHub is my first App, an open source project. Welcome to download. Monkey is a unofficial GitHub client.It includes the following functions. The rank of coders , the developer's ranking is based on follower. The rank of repositoriesrepositories , ranking is based on star. Login GitHub function,Follow developer and star repository,Support for viewing my GitHub news. The discovery module, including GitHub's repositories trending; my GitHub news; showcases; search; and other ranking data. -
22
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. -
23
bit CLI
Bit is a modern Git CLI
bit is an experimental modernized git CLI built on top of git that provides happy defaults and other niceties. Command and flag suggestions to help you navigate the plethora of options git provides you. Autocompletion for files and branch names when using bit add or bit checkout. Automatic fetch and branch fast-forwarding reduce the likelihood of merge conflicts. Suggestions work with git aliases. New commands like bit sync vastly simplify your workflow. Commands from git-extras such as bit release & bit info. Fully compatible with git allowing you to fallback to git if need be. Get insight into how bit works using bit --debug. -
24
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. -
25
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.
