Open Source Git Software - Page 8
Sort By:
Git Software
View 78 business solutions-
Gen AI apps are built with MongoDB AtlasMongoDB Atlas is the developer-friendly database used to build, scale, and run gen AI and LLM-powered apps—without needing a separate vector database. Atlas offers built-in vector search, global availability across 115+ regions, and flexible document modeling. Start building AI apps faster, all in one place.
-
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.
-
1
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. -
2
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. -
3
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. -
4
git-notify
Communicate important updates to your team via git commit messages
Communicate important updates to your team via git commit messages. Sometimes you need to communicate changes to other developers on your project. In a small team, a Slack message works okay, but in larger teams and distributed organizations (such as open-source projects), reaching everyone can be a pain. git-notify allows you to embed announcements into your git commit messages. And display them to another developer on a machine, far far away. Just add "git-notify:" to your git commit message, and anything that follows will be displayed when another developer pulls that commit, or switches from a branch that does not contain that commit to one that does. If you're using a merge or squash commit strategy on GitHub, you can also add them to the extended commit message when landing a PR. git-notify will display a message for every "git-notify:" prefix it finds in the commit log that was just pulled/merged/rebased/checked out. -
Simple, Secure Domain RegistrationRegister or renew your domain and pay only what we pay. No markups, hidden fees, or surprise add-ons. Choose from over 400 TLDs (.com, .ai, .dev). Every domain is integrated with Cloudflare's industry-leading DNS, CDN, and free SSL to make your site faster and more secure. Simple, secure, at-cost domain registration.
-
5
git-open
Type `git open` to open the GitHub page or website for a repository
Type git open to open the repo website (GitHub, GitLab, Bitbucket) in your browser. git open works with these hosted repo providers, git open --issue currently only works with GitHub, Visual Studio Team Services and Team Foundation Server. The preferred way of installation is to simply add the git-open script somewhere into your path (e.g. add the directory to your PATH environment or copy git-open into an existing included path like /usr/local/bin). Antigen will handle cloning the plugin for you automatically the next time you start zsh, and periodically checking for updates to the git repository. You can also add the plugin to a running zsh with antigen bundle paulirish/git-open for testing before adding it to your .zshrc. Add zgen load paulirish/git-open to your .zshrc file in the same function you're doing your other zgen load calls in. ZGen will take care of cloning the repository the next time you run zgen save, and will also periodically check for updates to the git repository. -
6
git-peek
git repo to local editor instantly
git peek is the fastest way to open a remote git repository in your local text editor. Use it when you want to browse or search other people's code with your own editor. Pass git peek a git repository or a github link, and it will quickly fetch and open it in your local editor. It stores the repository in a temporary directory and deletes it when you close the editor or git peek. If you don't pass git peek input, it will let you search Github repositories and show trending repositories. If you paste a link to a file on GitHub, it will quickly open the file in your local editor. If you pass it a GitHub repository, it fetches a tarball instead of using git and decompresses it while downloading it (streaming). From unscientific benchmarks, this is about 2x faster than cloning. While downloading & decompressing the tarball, it also downloads the specific file linked to (or the README.md) via JSDelivr's CDN. -
7
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. -
8
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. -
9
git-reports
Report git generator
Report generator log commits to the version control system git. Help me make it better with issues -
Secure User Management, Made Simple | FronteggFrontegg powers modern businesses with a user management platform that’s fast to deploy and built to scale. Embed SSO, multi-tenancy, and a customer-facing admin portal using robust SDKs and APIs – no complex setup required. Designed for the Product-Led Growth era, it simplifies setup, secures your users, and frees your team to innovate. From startups to enterprises, Frontegg delivers enterprise-grade tools at zero cost to start. Kick off today.
-
10
git-secrets
Prevents you from committing secrets and credentials into git
git-secrets is a Git extension that helps prevent secrets—API keys, credentials, tokens, private keys—from being accidentally committed into version control. It works by applying configurable regular-expression patterns over commit contents (and merge history) and rejecting commits or merges that violate the policy. The tool includes hooks that integrate into git commit and git merge, as well as commands to list, add, or remove secret patterns, and to scan existing history for leaks. Teams often deploy it as part of their developer toolchain to enforce a security guardrail: you catch leaks early rather than discovering them later. It is also often used in CI pipelines or continuous code quality checks to detect in-flight vulnerabilities. While git-secrets is not a full secrets management system, it plays a key role in defense-in-depth by preventing accidental exposure in source. -
11
git-sizer
Compute various size metrics for a Git repository
git-sizer computes various size metrics for a local Git repository, flagging those that might cause you problems or inconvenience. Is the repository too big overall? Ideally, Git repositories should be under 1 GiB, and (without special handling) they start to get unwieldy over 5 GiB. Big repositories take a long time to clone and repack, and take a lot of disk space. Avoid storing generated files (e.g., compiler output, JAR files) in Git. It would be better to regenerate them when necessary, or store them in a package registry or even a fileserver. Avoid storing large media assets in Git. You might want to look into Git-LFS or git-annex, which allow you to version your media assets in Git while actually storing them outside of your repository. Avoid storing file archives (e.g., ZIP files, tarballs) in Git, especially if compressed. Different versions of such files don't delta well against each other, so Git can't store them efficiently. -
12
github-changelog-generator
Automatically generate change log from your tags, issues, labels, etc.
Automatically generate change log from your tags, issues, labels and pull requests on GitHub. Fully automated changelog generation - This gem generates a changelog file based on tags, issues and merged pull requests (and splits them into separate lists according to labels) from octocat: GitHub. What’s the point of a changelog? To make it easier for users and contributors to see precisely what notable changes have been made between each release (or version) of the project. Why should I care? Because software tools are for people. "Changelogs make it easier for users and contributors to see precisely what notable changes have been made between each release (or version) of the project." Using Docker is an alternative to installing Ruby and the gem. -
13
gitin
commit/branch/workdir explorer for git
gitin is a minimalist tool that lets you explore a git repository from the command line. You can search from commits, inspect individual files and changes in the commits. It is an alternative and interactive way to explore the commit history. Also, you can explore your current state by investigating diffs, stage your changes and commit them. Fuzzy search (type / to start a search after running gitin command. Interactive stage and see the diff of files (gitin status then press enter to see diff or space to stage). Commit/amend changes (gitin status then press c to commit or m to amend). Interactive hunk staging (gitin status then press p). Explore branches with useful filter options (e.g. gitin branch press enter to checkout). Convenient UX and minimalist design. See more options by running gitin --help, also you can get help for individual subcommand. Linux and macOS are supported, Windows is not at the moment. -
14
gitjacker
Leak git repositories from misconfigured websites
Leak git repositories from misconfigured websites. Gitjacker downloads git repositories and extracts their contents from sites where the .git directory has been mistakenly uploaded. It will still manage to recover a significant portion of a repository even where directory listings are disabled. For educational/penetration testing use only. You will need to have git installed to use Gitjacker. -
15
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. -
16
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). -
17
gitslave
Coordinated multi-repository super-projects for Git
Gitslave is a script for coordinated version control of large projects combining code from multiple independent repositories using Git. More flexible than traditional git submodules, gitslave provides a simple wrapper around command-line git that manages a directory tree with multiple subsidiary ("slave") git repositories in sub-directories of a "master" git repository. Any git command run from the "gits" wrapper will be performed in all the git repositories; for example gits checkout -b newbranch will create the new branch in all repositories. Gitslave has been used for mid-sized product development with many slave repositories (representing different programs and plugins), branches, tags, and developers; and for single-person repositories tracking groups of .emacs and .vim repositories (in the latter case, it is basically used to keep the slave repositories up to date via a single command). -
18
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. -
19
go-git
go-git is a highly extensible git implementation library written in Go
go-git is a highly extensible git implementation library written in pure Go. It can be used to manipulate git repositories at low level (plumbing) or high level (porcelain), through an idiomatic Go API. It also supports several types of storage, such as in-memory filesystems, or custom implementations, thanks to the Storer interface. It's being actively developed since 2015 and is being used extensively by Keybase, Gitea or Pulumi, and by many other libraries and tools. After the legal issues with the src-d organization, the lack of update for four months and the requirement to make a hard fork, the project is now back to normality. The project is currently actively maintained by individual contributors, including several of the original authors, but also backed by a new company, gitsight, where go-git is a critical component used at scale. go-git aims to be fully compatible with git, all the porcelain operations are implemented to work exactly as git does. -
20
homeshick
git dotfiles synchronizer written in bash
In Unix, configuration files are king. Tailoring tools to suit your needs through configuration can be empowering. An immense number of hours is spent on getting these adjustments just right, but once you leave the confines of your own computer, these local optimizations are left behind. By the power of git, homeshick enables you to bring the symphony of settings you have poured your heart into with you to remote computers. With it you can begin to focus even more energy on bettering your work environment since the benefits are reaped on whichever machine you are using. However bare bones these machines are, provided that at least Bash 3 and Git 1.5 are available you can use homeshick. homeshick can handle multiple dotfile repositories. This means that you can install larger frameworks like oh-my-zsh or a multitude of emacs or vim plugins alongside your own customizations without clutter. -
21
Colección de páginas HTML5 con ejemplos y casos de uso del nuevo lenguaje de marcado así como de la combinación del mismo con estilos CSS de nivel 3, gráficos vectoriales SVG y script mediante ECMAScript 5.
-
22
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. -
23
libgit2
A cross-platform, portable, linkable Git implementation library
libgit2 is a portable, pure C implementation of the Git core methods provided as a re-entrant linkable library with a solid API, allowing you to write native speed custom Git applications in any language which supports C bindings. Libgit2 is developed with CMake, and this is be the easiest way to build a binary from the source. The CMake build system provides lots of options to configure the libgit2 build for your particular needs. It’s highly recommended that you build libgit2 as a static library for Xcode projects to simplify distribution significantly. libgit2 is used for powering Git GUI clients, such as gmaster and GitKraken and on Git hosting providers such as GitLab, Azure, GitHub, DevOps, among others. By clicking "merge pull request", we perform the merge. It is licensed under the GPLv2 license, so you can link it in its unmodified state with any type of software without releasing its source code. -
24
maven git commit id plugin
Maven plugin which includes build-time git repository information
git-commit-id-maven-plugin is a plugin quite similar to Build Number Maven Plugin for example but as the Build Number plugin at the time when I started this plugin only supported CVS and SVN, something had to be done. I had to quickly develop a Git version of such a plugin. For those who don't know the plugin, it basically helps you with the following tasks and answers related questions. The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. A detailed description of using the plugin is available in the Using the plugin document. All you need to do in the basic setup is to include that plugin definition in your pom.xml. For more advanced users we also prepared a guide to provide a brief overview of the more advanced configurations. Even though this plugin tries to be compatible with every Maven version there are some known limitations with specific versions. -
25
Python script to mirror a git repository with subversion It uses a basic common working directory, where git checkout the file for each commit of the master branch and then it will add, del, commit with a svn client.