Open Source Unix Shell Version Control Software

The Heirloom Project provides standard Unix utilities.

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.

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.

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.

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.

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.

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.

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.

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.

A project to provide change control for OpenDocument files via subversion under Unix. Can check in internal changes in files and allows users to recover any previous version, view logs and compare with older versions.

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.

EasyCM is to provide an easy way to install and setup an integrated SCM environment including Apache, SVN, Trac, and so on.

Sh scripts for (un)installing packages that can't be installed by default with apt-get.

Crossplatform framework for developing projects which provide services.

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.

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.

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.

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.

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.

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.

This project provides a coherent package of utilities that simplify the task of tagging, customising and packaging releases of code taken from CVS, together with documentation about release conventions and suggested practices.

CVS tools - set of utilities for users, project/build managers and system administrators. The tools use platform independent languages like bash, Perl, Python or Java. Platform support Win32/Cygwin and Linux based file systems. PROJECT MOVED. See Github user jaalto.

Color Subversion is a simple wrap on svn output, coloring each line regarding it's file status.

Corredor is a robust general framework for performing software test automation. The suite aims to simplify the set up, maintenance, and running of tasks, supporting remote distribution, parallel execution, & dependancy hierarchies.

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.