Open Source Windows Git Software - Page 7
Sort By:
Git Software for Windows
View 41 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.
-
$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.
-
1
Gitkube
Build and deploy docker images to Kubernetes using git push
Gitkube is a tool for building and deploying Docker images on Kubernetes using git push. After a simple initial setup, users can simply keep git push-ing their repos to build and deploy to Kubernetes automatically. Ideal for development where you can push your WIP branch to the cluster to test. Reference implementation for writing git-based automation on your server. Fork this repo and create your own CRD + controller + git remote hook that can do things on the Kubernetes cluster. No dependencies except native tooling (git, kubectl). Plug and play installation. Simple public key-based authentication. RBAC ready - Control access to git remotes using RBAC. Support for namespace-based multi-tenancy - Remotes can only deploy to their own namespace. No assumptions about the repository structure. -
2
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. -
3
Gitmal
A static page generator for repos
Gitmal is a static page generator that turns the contents of a Git repository into a clean, navigable HTML website, making it easier to share or showcase code outside of traditional Git hosting platforms. It reads repository metadata including files, commits, branches, and markdown, and produces a fully static set of pages with syntax-highlighted code, commit history, branch lists, and rendered documentation, so viewers can explore projects as if browsing a lightweight curated site. Designed for simplicity and performance, gitmal can be run locally or via a Docker container, and works across repositories of any size, producing fully self-contained output ready to be deployed to static web hosts. It supports themes and custom styles, allowing creators to personalize the look and feel of the generated site. For developers who want to archive, document, or display their code in a non-interactive context, gitmal provides a straightforward and configurable solution. -
4
Gitql
A git query language
Gitql is a Git query language. You can access the releases page and just grab the binary. If you want to compile itself just run go build. Gitql binary uses the embed file version.txt to outputs the gitql version command. On every release, the file content is replaced by the correct tag or git commit sha. -
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
Gradle Git
Git plugin for Gradle
Gradle‑Git bundles several plugins, most notably org.ajoberstar.grgit—for Gradle projects. It provides a Groovy/JGit wrapper (Grgit) to manage Git operations, plus support modules for GitHub Pages publishing and version-based release workflows. -
6
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. -
7
Gradle Libraries Plugin
This plugin allows to specify versions of external libraries
This plugin allows to specify versions of external libraries in a centralized place and use them across the project. It's specifically useful for Gradle multi-projects. This plugin also uses com.github.ben-manes.versions plugin to automatically update libraries once new releases are available. Run ./gradlew syncLibraries to create $rootDir/dependencies.json file with all currently known dependencies. Once dependencies.json file is in place by generating via syncLibraries task or just by manually creating it, all declared in dependencies.json libraries can be used in project files. It's not a secret that it's really hard to keep libraries up to date especially when there are dozens and sometimes hundreds of them. For that purpose, this plugin has update libraries task that will automatically check for available new versions of libraries. -
8
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. -
9
Just One Single History
Just One Single History
Combine the advantages of a monorepo with those of multirepo setups by leveraging a blazingly-fast, incremental, and reversible implementation of git history filtering. The partial repo will act as a normal git repository but only contain the files found in the subdirectory and only commits affecting those files. The partial repo supports both fetch as well as push operation. This helps not just to improve performance on the client due to having fewer files in the tree, it also enables collaboration on parts of the monorepo with other parties utilizing git's normal distributed development features. For example, this makes it easy to mirror just selected parts of your repo to public github repositories or specific customers. Simplify code sharing and dependency management. Beyond just subdirectories, Josh supports filtering, re-mapping and composition of arbitrary virtual repositories from the content found in the monorepo. -
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.
-
10
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)! -
11
Laragon
Powerful tool for modern apps: Django, Rails, Laravel, Node, Go, Java
Laragon makes coding more fun and easier. Instant setup - extremely fast, lightweight, intuitive, and powerful universal development enviroment for creating modern apps with many stacks: Ruby on Rails, Laravel, Django, Flask, MEAN and Spring Boot. Portable, reliable and Zero operation on MySQL, PostgreSQL, MongoDB, Memcached, Redis, PHP, Ruby, Python, Node.js and Java. -
12
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. -
13
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. -
14
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. -
15
VFS for Git
Virtual file system for Git, enable Git at enterprise scale
The Virtual Filesystem for Git (formerly GVFS) is an open source system that enables Git to operate at enterprise-scale. It makes using and managing massive Git repositories possible. VFS for Git virtualizes the filesystem beneath your Git repository so that Git tools see what appears to be a normal repository when, in fact, the files are not actually present on disk. VFS for Git only downloads files as they are needed. VFS for Git also manages Git's internal state so that it only considers the files you have accessed, instead of having to examine every file in the repository. This ensures that operations like status and checkout are as fast as possible. Git struggles to handle enterprise-scale repositories. Operations like cloning will slow to a crawl when you have millions of files in a repository, and even something as simple as getting your repository status will leave you waiting. -
16
-
17
Walle 2.0
Walle 2.0 web
Support multi-project, multi-environment one-click deployment and online, one-click quick rollback. Online order application, review, deployment, and real-time operation logs. Permissions, notifications, file fingerprints. Independent space resources like gitlab. Custom environment, environment variables. Project administrator, a notification mechanism, custom hooks in each process. Get through server management, grayscale release. Advanced gitlab-like user management mode. Online order application, review, grayscale release, real-time websocket. Walle allows users to release code and finally can not only choose jenkins! Support various web code releases, release and rollback of php, java, python, go and other codes can be completed with one click through the web. walle is a freely configurable project, more user-friendly, high-value, an open source online deployment system that supports git, multi-user, multi-language, multi-project, and multi-environment simultaneous deployment. -
18
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. -
19
ANT4GIT is an ANT task for GIT, a distributed source control management system (http://git-scm.com/).
-
20
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. -
21
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. -
22
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. -
23
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. -
24
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. -
25
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.
