Open Source Linux Git Software - Page 7
Sort By:
Git Software for Linux
View 17 business solutions-
Build AI Apps with Gemini 3 on Vertex AIVertex AI gives developers access to Gemini 3—Google’s most advanced reasoning and coding model—plus 200+ foundation models including Claude, Llama, and Gemma. Build generative AI apps with Vertex AI Studio, customize with fine-tuning, and deploy to production with enterprise-grade MLOps. New customers get $300 in free credits.
-
Cut Cloud Costs with Google Compute EngineSave on compute costs with Compute Engine. Reduce your batch jobs and workload bill 60-91% with Spot VMs. Compute Engine's committed use offers customers up to 70% savings through sustained use discounts. Plus, you get one free e2-micro VM monthly and $300 credit to start.
-
1
-
2
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. -
3
YaDT
Yet Another Diff Tool
YaDT - Yet another Diff Tool. It is another front-end for diff and in earlier versions diff3 utility. With YaDT you can compare and merge 2 and/or 3 files. YaDT is written on Tcl/Tk and wrapped in a single executable file with the help of sdx and tclkit. diff and cvs utilities are embedded inside YaDT. Also, YaDT supports Git and Mercurial repositories, but git and hg are not embedded inside YaDT, you should have git/hg executable in your path environment. -
4
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. -
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.
-
5
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. -
6
ANT4GIT is an ANT task for GIT, a distributed source control management system (http://git-scm.com/).
-
7
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. -
8
commitlint
Lint commit messages
commitlint checks if your commit messages meet the conventional commit format. commitlint helps your team adhere to a commit convention. By supporting npm-installed configurations it makes sharing of commit conventions easy. We're not a sponsored OSS project. Therefore we can't promise that we will release patch versions for older releases in a timely manner. If you are stuck on an older version and need a security patch we're happy if you can provide a PR. If something in between fails (like a new packages was added and needs to be published for the first time but you forgot) you can use lerna publish from-package to publish anythign that has not been published yet. We identify ease of adoption and developer experience as fields where there is room and need for improvement. The items on the roadmap should enhance commitlint regarding those aspects. -
9
composer-git-hooks
Easily manage git hooks in your composer config
Manage git hooks easily in your composer configuration. This command line tool makes it easy to implement a consistent project-wide usage of git hooks. Specifying hooks in the composer file makes them available for every member of the project team. This provides a consistent environment and behavior for everyone which is great. It is also possible to use to manage git hooks globally for every repository on your computer. That way you have a reliable set of hooks crafted by yourself for every project you choose to work on. You can also install it globally. This feels much more natural when cghooks is used with the newly added support for managing global git hooks. When a hook is a sequence of commands, it can be useful to stop the execution when a command fails. Custom hooks can be added to the custom-hooks array of the `config section. -
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.
-
10
diff2html
Pretty diff to html javascript library (diff2html)
Each diff provides a comprehensive visualization of the code changes, helping developers identify problems and better understand the changes. Each diff features a line-by-line and side-by-side preview of your changes. All the code changes are syntax highlighted using highlight.js, providing more readability. Similar lines are paired, allowing for easier change tracking. We work hard to make sure you can have your diffs in a simple and flexible way. The AI community building the future. Build, train and deploy state of the art models powered by the reference open source in natural language processing. Wrapper and helper adding syntax highlight, synchronized scroll, and other nice features. You can use it without syntax highlight or by passing your own implementation with the languages you prefer. Diff2Html can be used in various ways as listed in the distributions section. -
11
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. -
12
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. -
13
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. -
14
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. -
15
git-cal
github like contributions calendar on terminal
git-cal generates a terminal-friendly contribution calendar for your Git activity, echoing the familiar heatmap seen on hosting sites but rendered in plain text. It scans your repositories’ commit history and aggregates changes per day, then prints a compact grid that highlights streaks and quieter periods. The output works in standard shells, making it handy for dashboards, status emails, or a lightweight snapshot of productivity without opening a browser. Options typically let you choose time ranges, color intensity (where terminals support it), and which repositories to include. Because it reads local Git metadata, it respects your privacy and can include private work you don’t push to public remotes. For developers who like quick visual feedback in the CLI, git-cal turns raw commit timestamps into an at-a-glance activity portrait. -
16
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. -
17
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. -
18
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. -
19
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. -
20
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. -
21
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. -
22
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. -
23
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. -
24
git-reports
Report git generator
Report generator log commits to the version control system git. Help me make it better with issues -
25
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.
