Search Results for "shell 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. It is very lightweight, with...

...With git-flow, each type of branch has explicit purpose and merge rules: features merge back into develop, release branches prepare towards master, and hotfixes branch off master for urgent repairs. The repository you referenced provides the actual shell scripts (and wrappers) implementing sub‐commands like git flow feature start, git flow release finish, etc., making the workflow operational rather than purely conceptual.

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

nodebrew is a straightforward version manager for Node.js that installs into your home directory and lets you switch Node versions with a single command. It can download official binaries or build from source, track multiple installed versions, and set a global “current” version by updating your shell PATH. The tool keeps Node and npm isolated per version, which prevents project conflicts and makes upgrades or rollbacks reversible. Commands for listing, aliasing, and uninstalling versions keep long-lived environments tidy, while simple shims make the active toolchain transparent to existing scripts. Because nodebrew is lightweight and has minimal external dependencies, it’s popular on servers, CI agents, and developer laptops alike. ...

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

OFormsCI is a set of tools to form a complete tool chain for continuous integration with Git, Jenkins, Oracle Forms/Reports and WebLogic server.

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.