Open Source Linux Git Software - Page 8
Sort By:
Git Software for Linux
View 17 business solutions-
Enterprise-grade ITSM, for every businessFreshservice is an intuitive, AI-powered platform that helps IT, operations, and business teams deliver exceptional service without the usual complexity. Automate repetitive tasks, resolve issues faster, and provide seamless support across the organization. From managing incidents and assets to driving smarter decisions, Freshservice makes it easy to stay efficient and scale with confidence.
-
Secure File Transfer for Windows with Cerberus by RedwoodCerberus supports unlimited users and connections on a single IP, with built-in encryption, 2FA, and a browser-based web client — all deployable in under 15 minutes with a 25-day free trial.
-
1
git-remote-dropbox
A transparent bridge between Git and Dropbox
git-remote-dropbox is a Git remote helper that lets Dropbox act like a real Git remote. It provides a transparent bridge between Git and a Dropbox folder or shared Dropbox folder. After installation and login, users can clone from or push to remote URLs that use the dropbox scheme. The helper preserves traditional Git remote guarantees, including atomic behavior even when multiple people operate on the repository. It can automatically create the repository directory the first time a user pushes. It also includes a git dropbox management tool for authentication, repository management, app-folder access, and multiple Dropbox accounts. -
2
git-reports
Report git generator
Report generator log commits to the version control system git. Help me make it better with issues -
3
git-secret
A bash-tool to store your private data inside a git repository
There’s a well-known issue with deploying and configuring software on servers: generally, you have to store your private data (such as database passwords, application secret-keys, OAuth secret keys, etc) outside of the git repository. If you do choose to store these secrets unencrypted in your git repo, even if the repository is private, it is a security risk to copy the secrets everywhere you check out your repo. These files are not version controlled. Filenames, locations, and passwords change from time to time, or new information appears, and other information is removed. When secrets are stored separately from your repo, you can not tell for sure which version of the configuration file was used with each commit or deploy. When building the automated deployment system there will be one extra step: download and place these secret-configuration files where they need to be. This also means you have to maintain extra secure servers where all your secrets are stored. -
4
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. -
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.
-
5
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. -
6
Allows to transparently encrypt repository contents with AES 256. The main advantage is that no additional software needed to be installed in untrusted location. Files are automatically encrypted on the fly when doing git push from trusted location.
-
7
gitfs
Version controlled file system
gitfs is a FUSE file system that fully integrates with git. You can mount a remote repository's branch locally, and any subsequent changes made to the files will be automatically committed to the remote. gitfs was developed by the awesome engineering team at Presslabs, a Managed WordPress Hosting provider. gitfs was designed to bring the full powers of git to everyone, no matter how little they know about versioning. A user can mount any repository and all their changes will be automatically converted into commits. gitfs will also expose the history of the branch you're currently working on by simulating snapshots of every commit. gitfs is useful in places where you want to keep track of all your files, but at the same time you don't have the possibility of organizing everything into commits yourself. A FUSE filesystem for git repositories, with local cache. We provide packages for the major Ubuntu releases and MacOS. -
8
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. -
9
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). -
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.
-
10
gitstatus
Git status for Bash and Zsh prompt
gitstatus is a 10x faster alternative to git status and git describe. Its primary use case is to enable fast git prompt in interactive shells. Heavy lifting is done by gitstatusd -- a custom binary written in C++. It comes with Zsh and Bash bindings for integration with shell. The easiest way to take advantage of gitstatus from Zsh is to use a theme that's already integrated with it. For example, Powerlevel10k is a flexible and fast theme with first-class gitstatus integration. If you install Powerlevel10k, you don't need to install gitstatus. This will give you a basic yet functional prompt with git status in it. It's over 10x faster than any alternative that can give you comparable prompt. In order to customize it, set PROMPT and/or RPROMPT at the end of ~/.zshrc after sourcing gitstatus.prompt.zsh. Insert ${GITSTATUS_PROMPT} where you want git status to go. -
11
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. -
12
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. -
13
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.
-
14
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. -
15
mergepbx
script for merging XCode project files in git
Tracking a Xcode project in a version control system is annoying. Simply adding files can lead to merge conflicts that have to be solved manually, although it would be possible to resolve the conflict automatically if the merge algorithm would be aware of the structure of Xcode's project file. After long and annoying merge sessions in one of my projects, I came to the conclusion, that writing a merge driver for git which understands the structure of the project file would be a worthwhile endeavour, as it would save me from solving the merge conflicts for my co-workers. Unfortunately, that script was finished only after the project ended. However, as I didn't want to let the work go to waste, this script is now published as open source under the GNU GPL 3. This script needs knowledge about the structure of Xcode's project. However, there doesn't seem to be any documentation (and I would be surprised if there were any). -
16
meta
Tool for turning many repos into a meta repo
Tool for turning many repos into a meta repo. why choose many repos or a monolithic repo, when you can have both with a meta repo? meta is powered by plugins that wrap common commands, letting you execute them against some or all of the repos in your solution at once. meta is built on loop, and as such inherits loops ability to easily target a particular set of directories for executing a common command (eg meta git status --include-only dir1,dir2. See loop for more available options). meta is a tool for managing multi-project systems and libraries. It answers the conundrum of choosing between a mono repo or many repos by saying "both", with a meta repo! Give every engineer on your team the same project setup, regardless of where it's cloned. Execute arbitrary commands against many repos to manage your projects. Easily wrap commands for working with any platform, not just Node! -
17
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.
-
18
monorepo
Git monorepo management
-
19
n
Node version management
Node.js version management: no subshells, no profile setup, no convoluted API, just simple. n is not supported natively on Windows. There are a variety of ways of specifying the target Node.js version for n commands. Most commands use the latest matching version, and n ls-remote lists multiple matching versions. n downloads a prebuilt Node.js package and installs to a single prefix (e.g. /usr/local). This overwrites the previous version. The bin folder in this location should be in your PATH (e.g. /usr/local/bin). The downloads are kept in a cache folder to be used for reinstalls. The downloads are also available for limited use using n which and n run and n exec. The global npm packages are not changed by the install, with the exception of npm itself which is part of the Node.js install. -
20
pre-commit-hooks
Some out-of-the-box hooks for pre-commit
Some out-of-the-box hooks for pre-commit. Using pre-commit-hooks with pre-commit. Instead of loading the files, simply parse them for syntax. A syntax-only check enables extensions and unsafe constructs which would otherwise be forbidden. Using this option removes all guarantees of portability to other yaml implementations. Detect symlinks which are changed to regular files with a content of a path that that symlink was pointing to. This usually happens on Windows when a user clones a repository that has symlinks but they do not have permission to create symlinks. Limits checked files to those indicated as staged for addition by git. Check all listed files not just those staged for addition. -
21
repoheat
Creates a commit heatmap across several repositories.
Creates a commit heatmap across several Git and Mercurial repositories. Scans a list of paths recursively for Mercurial and Git repositories and creates a commit heat map for a specific year. Optionally reports a combined heat map for all found repositories, or a separate heat map for each repository. Comes with options to filter for specific authors or apply an authormap file to combine different authors into one heat map. -
22
sbdiff
sbdiff is a frontend for (GNU) diff with colorized side by side output
sbdiff is a frontend for (GNU) diff. It compares files and directories line by line, outputs the files side-by-side in two columns and colorizes the differences. Because it is a console application, no GUI is necessary. -
23
Screwdriver is an Simple Dis-Integrated Development Environment (SDIDE) used for programming in Python, PySide, Bash and Other object-oriented programming technologies. Source code management Interface can Push Up to 97 branches into the Git server. Reclaim your favourite Linux text editor.
-
24
skinny
A local subversioning command line tool.
A local subversioning command line tool, written for those who find git troublesome and difficult to use for simple backups and snapshots of projects. The name is derived form being a small tool than git (which is really muscular), but skinny provide you easy to learn four commands and only used for local source management, commit log init restore ..thats it four commands no big deal. But its power lies in its simplicity formanaging Directory and Project States by making Snaposhots using a command line. -
25
sourcerer.io
Sourcerer app makes a visual profile from your GitHub and git repos
Sourcerer app makes a visual profile from your GitHub and git repositories. Creating your profile is just the first step for us at Sourcerer. Some of the things on our roadmap include engineers to follow and learn from, technology and libraries you should know about, and projects that could use your help. The app looks at repos locally on your machine, and then sends stats to sourcerer.io. The best way to verify is to look at the code. Protobuf messages declared in src/main/proto/sourcerer.proto is a good start as it describes the client-server protocol. The Sourcerer app does not upload source code anywhere, and it never will. Visual presentation your development experience. Detection of more than 1,000 libraries in code with per-line statistics. Support of 100 languages (even exotic ones like COBOL). Finally! Summary of all repositories you've contributed to.
