Open Source Linux Git Software - Page 3
Sort By:
Git Software for Linux
View 17 business solutions-
Application Monitoring That Won't Slow Your App DownFull APM with errors, performance, logs, and uptime monitoring. 99.999% uptime SLA on the platform itself.
-
Try Google Cloud Risk-Free With $300 in CreditUse your credit across every product. Compute, storage, AI, analytics. When it runs out, 20+ products stay free. You only pay when you choose to.
-
1
Docker Gitlab
Dockerized GitLab
Dockerfile to build a GitLab image for the Docker opensource container platform. GitLab CE is set up in the Docker image using the install from source method as documented in the the official GitLab documentation. For other methods to install GitLab please refer to the Official GitLab Installation Guide which includes a GitLab image for Docker. Docker is a relatively new project and is active being developed and tested by a thriving community of developers and testers and every release of docker features many enhancements and bugfixes. Given the nature of the development and release cycle it is very important that you have the latest version of docker installed because any issue that you encounter might have already been fixed with a newer docker release. Install the most recent version of the Docker Engine for your platform using the official Docker releases. -
2
Fix All Conflicts
Easy-to-use CUI for fixing git conflicts
I never really liked any of the mergetools out there so I made a program that is somewhat easier to use.fac operates much like git add -p . It has a prompt input at the bottom of the screen where the user inputs various commands. The above key-bindings and various behaviors can be altered by creating a .fac.yml file in your home directory. Please refer to the configuration README.md for more information. -
3
Fork and Pull Request Workflow
Quick reference guide on fork and pull request workflow
This document describes how developers may contribute pull requests to an upstream repository and how upstream owners may merge pull requests from contributors according to the very popular fork and pull request workflow followed in many projects on GitHub. The download buttons above download version 0.6.0 (the latest stable release) of this document. Every project has a main development branch where the developers push commits on a day-to-day basis. Usually, the main development branch is master but some projects choose to have develop or trunk or another branch for day-to-day development activities. We refer to this main development branch as the main development branch throughout this document to keep the text general. However in the command examples and ASCII-diagrams, we use master as an example of the main development branch. -
4
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. -
Earn up to 16% annual interest with Nexo.Generate interest, access liquidity without selling, and execute trades seamlessly. All in one platform. Geographic restrictions, eligibility, and terms apply.
-
5
Git Subtree Splitter
Split a repository to read-only standalone repositories
Split a repository to read-only standalone repositories. splitsh-lite replaces the subtree split Git built-in command to make splitting a monolithic repository to read-only standalone repositories easy and fast. Both strategies work well and both have drawbacks as well. splitsh helps use both strategies by providing tools that automatically synchronize a monolithic repository to standalone repositories in real-time. splitsh-lite is a sub-project that provides a faster implementation of the git subtree split command, which helps create standalone repositories for one or more sub-directories of a main repository. If you want to learn more about monorepo vs manyrepos, watch this 4-minute lightning talk I gave at dotScale (or read the slides)... or watch the longer version from DrupalCon. "The Monorepo - Storing your source code has never been so much fun" is also a great resource. -
6
Git Updater
This WP plugin will update GitHub, Bitbucket, GitLab, etc.
This plugin was originally designed to simply update any GitHub-hosted WordPress plugin or theme. Your plugin or theme must contain a header in the style.css header or in the plugin's header denoting the location on GitHub. API plugins for Bitbucket, GitLab, Gitea, and Gist are available. API plugins are available for a one-click install from the Add-Ons tab. This update reincorporates all functionality into the Git Updater plugin and splits out the API components into individual API plugins. There is a 14-day free trial and a 30-day no questions asked money-back guarantee. Programming is a great creative outlet. As the Git Updater family of products has grown more developers are using it in their workflow and support requests are increasing. I made a decision to rebrand and monetize it. -
7
GitHub Extension for Visual Studio
GitHub Extension for Visual Studio
The GitHub Extension for Visual Studio provides GitHub integration in Visual Studio 2015 and newer. Most of the extension UI lives in the Team Explorer pane, which is available from the View menu. Use GitHub and Visual Studio to bring CI / CD source control and workflows closer to your code. GitHub compatibility is now integrated into Visual Studio. Get GitHub for Visual Studio set up to bring the GitHub flow to Visual Studio. Authenticate to GitHub.com or GitHub Enterprise, keep the extension up-to-date, and review your preferred settings. Use GitHub for Visual Studio to manage your projects and work with pull requests. -
8
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. -
9
Gitolite
Hosting git repositories
Gitolite is a lightweight Git server and access-control system that lets many human users share a single Unix account while enforcing fine-grained permissions. Configuration is “as code”: you manage users’ SSH keys and per-repo rules in a special admin repository, then push to apply changes instantly. Permissions are precise—read, write, or force-push can be allowed or denied per repository, branch, tag, or arbitrary ref patterns—so sensitive branches can be protected. Delegation features let large organizations hand off subsets of administration without giving away global control, and “wild” repositories make self-service project creation possible within policy. Hooks, logging, and auditing are baked in, giving visibility into who pushed what and when. Because it rides on plain SSH and standard Git, it’s fast, portable, and easy to host on anything from a low-power VPS to an enterprise server. -
Gemini 3 and 200+ AI Models on One PlatformBuild generative AI apps with Vertex AI. Switch between models without switching platforms.
-
10
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. -
11
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. -
12
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)! -
13
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. -
14
PHP GitHub API
A simple PHP GitHub API client, Object Oriented, tested and documented
A simple PHP GitHub API client, Object Oriented, tested and documented. Uses GitHub API v3 & supports GitHub API v4. The object API (v3) is very similar to the RESTful API. Object Oriented wrapper for GitHub API, written with PHP. Light and fast thanks to lazy loading of API classes. Extensively tested and documented. We are decoupled from any HTTP messaging client with help by HTTPlug. To integrate this library in laravel Graham Campbell created graham-campbell/github. See the installation instructions to get started in laravel. -
15
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. -
16
QtPass
QtPass is a multi-platform GUI for pass, the standard unix password
QtPass is part of the pass ecosystem. This means you are not stuck with QtPass, you can use the same password store with many clients. Password management should be simple and follow Unix philosophy. With pass, each password lives inside of a gpg encrypted file whose filename is the title of the website or resource that requires the password. These encrypted files may be organized into meaningful folder hierarchies, copied from computer to computer, and, in general, manipulated using standard command line file management utilities. Contrary to many Free, Libre and OpenSource password managers, pass and by extension QtPass are not bound to one user or device. Since we are based on GnuPG we have multi-key, multi recipient encryption out of the box. The use of external encryption devices like OpenPGP or x509/CMS based smartcards or USB tokens and per-folder ACL makes it easy to grant or take away privileges from users. -
17
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. -
18
Watchtower
A process for automating Docker container base image updates
With watchtower you can update the running version of your containerized app simply by pushing a new image to the Docker Hub or your own image registry. Watchtower will pull down your new image, gracefully shut down your existing container and restart it with the same options that were used when it was deployed initially. Watchtower is an application that will monitor your running Docker containers and watch for changes to the images that those containers were originally started from. If watchtower detects that an image has changed, it will automatically restart the container using the new image. With watchtower you can update the running version of your containerized app simply by pushing a new image to the Docker Hub or your own image registry. Watchtower will pull down your new image, gracefully shut down your existing container and restart it with the same options that were used when it was deployed initially. -
19
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. -
20
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. -
21
asdf
Extendable version manager with support for Ruby, Node.js, Elixir, etc
Manage multiple runtime versions with a single CLI tool. Manage each of your project runtimes with a single CLI tool and command interface. asdf is a CLI tool that can manage multiple language runtime versions on a per-project basis. It is like gvm, nvm, rbenv & pyenv (and more) all in one! Simply install your language's plugin! Large ecosystem of existing runtimes & tools. Simple API to add support for new tools as you need! Support for existing config files .nvmrc, .node-versions, .ruby-version for smooth migration! .tool-versions to manage all your tools, runtimes, and their versions in a single, sharable place. Supports Bash, ZSH, Fish & Elvish with completions available. Provides a GitHub Action to install and utilize your .tool-versions in your CI/CD workflows. -
22
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. -
23
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. -
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
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.
