Search Results for "scripts"

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. ...

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.

...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.

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.

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

Braincracks acts like a continuous snapshoting filesystem / versioning filesystem. It monitors folders for files changes (each X seconds) and saves a copy of files when they change. It is made of 3 Bourne Shell scripts (1 bin, 1 daemon, 1 service).

A set of scripts named "svnexport" is intended to update the Web site from the Subversion repository by using "svn export [options]" command. You can work through a Web interface or from the command line.

gc-utils is a small set of scripts that let you import and update CVS repositories into git very easy and let you export patches back into a CVS working copy.

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.

SAVT is a set of shell scripts which allow you to put config files under version control using Subversion with support for metadata versioning (permissions, ownership) and share them with certain host types.

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.