Open Source Unix Shell Version Control Software for Mac
Sort By:
Unix Shell Version Control Software for Mac
View 29 business solutionsBrowse free open source Unix Shell Version Control Software for Mac and projects below. Use the toggles on the left to filter open source Unix Shell Version Control Software for Mac by OS, license, language, programming language, and project status.
-
Host LLMs in Production With On-Demand GPUsDeploy your model, get an endpoint, pay only for compute time. No GPU provisioning or infrastructure management required.
-
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
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. -
2
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. -
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
git-flow (AVH Edition)
AVH Edition of the git extensions to provide high-level repository ops
A collection of Git extensions to provide high-level repository operations for Vincent Driessen's branching model. This fork adds functionality not added to the original branch. For those who use the Bash or ZSH shell, you can use my fork of git-flow-completion which includes several additions for git-flow (AVH Edition), or you can use the original git-flow-completion project by bobthecow. Both offer tab-completion for git-flow subcommands and branch names with my fork including tab-completion for the commands not found in the original git-flow. For a wide variety of commands hooks or filters can be called before and after the command. The files should be placed in .git/hooks In the directory hooks you can find examples of all the hooks available. You can easily publish a feature you are working on. The reason can be to allow other programmers to work on it or to access it from another machine. -
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
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.
-
6
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. -
7
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. -
8
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. -
9
nvm.fish
The Node.js version manager you'll adore, crafted just for Fish
nvm.fish is a Node.js version manager tailored specifically for the Fish shell, allowing users to install and switch between multiple Node.js versions seamlessly. -
Gemini 3 and 200+ AI Models on One PlatformBuild generative AI apps with Vertex AI. Switch between models without switching platforms.
-
10
This is an add-on to stow. If the "make install" didn't work with DESTDIR argument(or use another installer), stow-jail would close the installer command to the sandbox(unionfs+chroot),in this way all go to the "/stow/package_name" directory.
-
11
bfm
BigFileManager - Manage files outside of your VCS
This tool is intended to manage big files out of your VCS but in your workarea. It's like mercurial largefile extension but independend of any VCS. Instead of the big file itself only a list of filenames with their checksums (md5) are committed to the VCS. The BFM can check for missing or outdated bigfiles and downloads them from a server using CURL. -
12
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.
-
13
-
14
DevOps Bash Tools
800+ DevOps Bash Scripts - AWS, GCP, Kubernetes, Docker, CI/CD, APIs
Scripts for many popular DevOps technologies, see Inventory below for more details. Advanced configs for common tools like Git, vim, screen, tmux, PostgreSQL psql etc. CI configs for most major Continuous Integration products (see CI builds page) CI scripts for a drop-in framework of standard checks to run in all CI builds, CI detection, accounting for installation differences across CI environments, root vs user, virtualenvs etc. API scripts auto-handling authentication, tokens and other details to quickly query popular APIs with a few keystrokes just supplying the /path/endpoint. Advanced Bash environment - .bashrc + .bash.d/*.sh - aliases, functions, colouring, dynamic Git & shell behaviour enhancements, automatic pathing for installations and major languages like Python, Perl, Ruby, NodeJS, Golang across Linux distributions and Mac. See .bash.d/README.md. Installs the best systems packages. -
15
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. -
16
Git Blame Someone Else
Blame someone else for your bad code
git-blame-someone-else is a humorous Git utility created as a joke to let developers attribute problematic code to someone else. It modifies both the author and committer information of a commit, making it appear as though another contributor is responsible for the changes. While not intended for production repositories, it demonstrates how Git’s metadata can be manipulated for fun or demonstration purposes. The project highlights how easily commit authorship can be altered, serving as both a lighthearted tool and a reminder about the importance of trust in version control history. It’s written in shell script and is lightweight, requiring only Git and basic system tools to run. Despite being a novelty project, its popularity shows how developers appreciate humor injected into the programming ecosystem. -
17
Git Goodies
Git Goodies: At-A-Glance, Efficient, and Aesthetically Pleasing Git
Git Goodies: At-A-Glance, Efficient, and Aesthetically Pleasing Git Shortcuts. gg helps you work with git more efficiently, saving you keystrokes for your most prized projects. Think of gg as a wrapper for the git commands that you run all the time; a wrapper that adds functionality and is aesthetically pleasing. There's more to the package than just shortcuts or aliases. For example, the gg s command presents you with an easy to look at a quick glance status of your repository. In addition, there are aesthetic changes that increase the intuitiveness of Git itself. You can see the current local branch and its respective remote branch, the latest commit hash and message, the local repository's position in relation with the respective remote repository (alerting you that you should push two commits to reach up-to-date status with the remote repository), the status of staging and commits, and the commits that waiting to be pushed. -
18
Git Katas
A set of exercises for deliberate Git Practice
This repository is a collection of Git exercises. The concept is stolen without shame from Schauderhaft.de. Unfortunately, they have not maintained the system - and we need more good Git exercises. The exercises are designed for use when we are teaching Git courses. You should be able to use them as self-contained exercises that will allow you to keep your Git skills sharp. Exercises starting with basic are entry-level - other exercises vary greatly in difficulty. If you are coming to this repository for some basic Git knowledge, we recommend going through the exercises in the following order. This is the order that Jan Krag at Praqma teaches Git and might change over time. There are more exercises than this, but these should take you through everything you need to be able to use Git effectively in your day to day life. -
19
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. -
20
Informative git prompt for bash and fish
An informative and fancy bash prompt for Git users
This prompt is a port of the "Informative git prompt for zsh". A bash prompt that displays information about the current git repository. In particular the branch name, difference with remote branch, number of files staged, changed, etc. The advantage of this approach is, that you only need to specify the parts, that are different to the Default theme. You can set the GIT_PROMPT_SHOW_UNTRACKED_FILES variable to no or normal to speed things up if you have lots of untracked files in your repository. This can be the case for build systems that put their build artifacts in the subdirectory structure of the git repository. Setting it to all will count all untracked files, including files listed in .gitignore. The most settings are now stored in theme files. To select a theme, set the variable GIT_PROMPT_THEME to the name of the theme located in <INSTALLDIR>/themes without the extension .bgptheme. -
21
JViewCVS is a Java-based(JSP) web application for viewing a CVS repository. The goal of this project is to create the same functionality as viewcvs, but written in JSP.
-
22
A web interface based on PHP/MySQL/XML to manage a Internationalization/Localization team and work. eg. Job Assignment, Proofreading, Glossary...
-
23
QB (Quellcode Bahn) is a software that manage the operations on the source of the programs you develop, with a versioned repository. QB manage the deploy of your program, taking it from the repository and putting it wherever you want with test phase.
-
24
The SoftChange project will create software to summarize and analyze software changes in CVS repositories and defect tracking systems (Bugzilla/GNATS).
-
25
SvnCrawler is a tool for analysis of Subversion (SVN) repositories. The project includes different plug-ins for generating csv reports, rss feeds and more. Creating a new plug-in takes only a few bash lines. More info: http://svncrawler.sourceforge.net
