Open Source Unix Shell Version Control Software
Sort By:
Unix Shell Version Control Software
View 78 business solutionsBrowse free open source Unix Shell Version Control Software and projects below. Use the toggles on the left to filter open source Unix Shell Version Control Software by OS, license, language, programming language, and project status.
-
Get Avast Free Antivirus | Your top-rated shield against malware and online scamsOur antivirus software scans for security and performance issues and helps you to fix them instantly. It also protects you in real time by analyzing unknown files before they reach your desktop PC or laptop — all for free.
-
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.
-
1
-
2
Husky
Git hooks made easy
Husky is a tool that makes handling Git hooks a lot easier, and lets you run the scripts you want at those stages. It works by including an object right within your package.json file. This then configures Husky so that it runs the scripts you specify. After that, it's Husky's responsibility to manage at which point in the Git lifecycle your scripts will run. Husky helps to improve your commits, lets you run tests, lint code and more when you commit or push. It is very lightweight, with zero dependencies and is capable of supporting all Git hooks. -
3
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. -
4
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. -
MongoDB Atlas | Run databases anywhereMongoDB Atlas allows you to build and run modern applications across 125+ cloud regions, spanning AWS, Azure, and Google Cloud. Its multi-cloud clusters enable seamless data distribution and automated failover between cloud providers, ensuring high availability and flexibility without added complexity.
-
5
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. -
6
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. -
7
pyenv
Simple Python version management
pyenv is a tool for the simple management of Python versions: it lets you easily switch between different Python versions, offering support for per-project Python versions. pyenv is an uncomplicated, unobtrusive tool that simply works, and follows the UNIX tradition of single-purpose tools that do one thing well. Unlike other similar tools, pyenv does not depend on Python itself. Having been made from pure shell scripts, it's safe from a Python bootstrap problem. It doesn't need to be loaded into your shell thanks to its shim approach, and can manage virtualenv for you. pyenv is a fork of rbenv and ruby-build, modified for Python. -
8
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. -
9
GIT quick statistics
An efficient way to access various statistics in git repository
git-quick-stats is a simple and efficient way to access various statistics in a git repository. Any git repository may contain tons of information about commits, contributors, and files. Extracting this information is not always trivial, mostly because there are a gadzillion options to a gadzillion git commands. For those who prefer to utilize command-line options, git-quick-stats also has a non-interactive mode supporting both short and long options. You can change to the legacy color scheme by toggling the variable _MENU_THEME between default and legacy. You can set variable _GIT_LIMIT for limited output. It will affect the "changelogs" and "branch tree" options. You can also exclude files from the stats. Note that it works with any alphanumeric, glob, or regex that git respects. -
Build Securely on AWS with Proven FrameworksMoving to the cloud brings new challenges. How can you manage a larger attack surface while ensuring great network performance? Turn to Fortinet’s Tested Reference Architectures, blueprints for designing and securing cloud environments built by cybersecurity experts. Learn more and explore use cases in this white paper.
-
10
Git-FTP
Uses Git to upload only changed files to FTP servers
If you use Git and you need to upload your files to an FTP server, Git-ftp can save you some time and bandwidth by uploading only those files that changed since the last upload. It keeps track of the uploaded files by storing the commit id in a log file on the server. It uses Git to determine which local files have changed. You can easily deploy another branch or go back in the Git history to upload an older version. git-ftp was not designed as centralized deployment tool. While a commit is being pushed and uploaded to the FTP server, all files belonging to that revision must remain untouched until git-ftp has successfully finished the upload. Otherwise, the contents of the uploaded file will not match the contents of the file referenced in the commit. -
11
typewritten
A minimal, lightweight, informative zsh prompt theme
A minimal, lightweight, informative zsh prompt theme. Clone the typewritten repository somewhere you can easily link. I recommend creating a .zsh directory at root. typewritten is customizable in many ways. Prompt customization, everything to do with how and where the info is displayed. Prompt color customization set a custom color for any of the prompt sections. -
12
Shell Package Manager
Install packages that apt-get can't.
Sh scripts for (un)installing packages that can't be installed by default with apt-get. -
13
simple rdist rcs and tools , srtools
simple rdist rcs and tools , srtools , synchronizing
srtools is a set of simple remote tools. the main two to mention: simple rdist distributes files or commands across hosts. srdist(1) understands rcs(1) files and host based files. there are several other tools see README. rcs tools has a few things , like "late-checkins" to check for files that one forgot to check in an dorev to force check in / do easy check in (avoiding complicated options). host based files is a way to allow hosts to distribute all files without clobbering host specific files. and with that ... srtools(1) makes partially synchronizng hosts easy. Also can be a far easier way to do incremental or nightly backups. Also an easy way to have multiple hosts interact. README is visible on file download page EXAMPLE: $rcssrdist file (file was broadcased to default hosts list that are up. if a rcs pair existed it was taken care of. existence of directory on other hosts was checked (common mistakes checked) -
14
Provide secure and stable OS, based on highly modified Linux Kernel, own package system, like "BSD Ports". Compatible with x86, Power PC. Easy to use of any level users. Complete Documentantion in many languages. 99% compatible with Windows.
-
15
CSSC is a clone of the Unix SCCS tool suite. CSSC is useful for working with existing source respositories that are already in SCCS format.
-
16
-
17
aepro is a dependency maintenance tool for progres4gl. It is intended to be used in conjuction with aegis (aegis.sourceforge.net), a source code configuration tool. It (re)compiles progres4GL programs whose sourcecode has changed.
-
18
CvsKnit is a toolset to automate knitting up CVS repositories from existing source packages. This is a sub-project of minix-up project (SF.jp).
-
19
rcss
rcss makes using (RCS) (S)imple
rcss - rcs simplified. RCS is revision control. While the newer revision controls like git have taken the world by storm, I find as a systems administrator that I don't need all the features of git, I need some thing simple and that stays on my server and is simple and easy to use. RCS fit the bill for me for revision control. RCS didn't make it easy to do things like compare, revert. So I wrote rcss, to make working with rcs MUCH simpler, at least for myself. I hope you find it as useful as I have. -
20
A plug-in element for CruiseControl to detect tag related modifications in a source code repository (CVS).
-
21
The Ape Base Compile System is a set of bash scripts to leverage both ESP EPM (http://www.epmhome.org/) and MREPO (http://dag.wieers.com/home-made/mrepo/) in maintaining applications such as as Apache HTTPD, MySQL or PHP on Red Hat based systems.
-
22
The aim of this project is to make it easier to keep the source code updated with the server on projects that use CVS. Keeping up to date source files on SourceForge.com projects will be automated.
-
23
BTS is a Build Template System designed for building packages for th common packing systems in use by current distributions based on a single XML package description. We are finally restarting development after a long break due to NeOS work.
-
24
CODESH
Automatic persistent logbooks for Linux shell sessions (bash, tcsh...)
The CODESH (COllaborative DEvelopment SHell) project provides an automatic persistent logbook for sessions of personal command-line work by recording what and how is being done: for private use/reuse and for sharing selected parts with collaborators. -
25
The enclosed Python scripts differ from most other commit notification solutions in that they coalesce all of the commit operations from a single \\\"cvs commit\\\" command into a single email. Most other solutions will send one email per directory.
