Only npm installs if package.json has been modified
Only run 'npm install' if dependencies changed
No description provided.
A little library for asserting types and values, with zero dependencies.
Tells you whether or not dependencies in package.json have been changed.
No description provided.
A lightweight cache for file metadata, ideal for processes that work on a specific set of files and only need to reprocess files that have changed since the last run
A simple hook to debug various Reactjs hooks which supports dependency as the second argument.
Only pass through changed files
Utilities for watching file trees.
Run ESLint on your changes only
Delightful JavaScript Testing.
Tiny LiveReload server, background-friendly
Delightful JavaScript Testing.
A natural language date parser in Javascript
React Native Camera Roll for iOS & Android
Enables the use of Chromatic Turbosnap in vite storybook projects
Run a command if a file changes via Git hooks
Intuitive magical memoization library with Proxy and WeakMap
Only pass .less files through the gulp stream if they or their dependencies have changed
Livereload for webpack
Run commands and scripts after git pull
Lerna-Lite changed commmand - List local packages that have changed since the last tagged release
multipart/form-data parser which supports streaming
Allow your Redmine installation to be notified when changes have been pushed to a Github repository.
Watches for changes and compiles Haml, Sass, Scss, and Coffeescript
Diff::LCS computes the difference between two Enumerable sequences using the McIlroy-Hunt longest common subsequence (LCS) algorithm. It includes utilities to create a simple HTML diff output format and a standard diff-like tool. This is release 2.0, which has significant breaking changes (removal of deprecations and workarounds) and requires at least Ruby 3.2 or higher. See full details in the `CHANGELOG`, but users of diff-lcs should not notice any significant changes to the APIs. ==== To Install:
Install a post-merge hook for git that tells you when the Gemfile changed or a migration was added
Downloads and installs chromedriver2 from google's page and uses it for running the selenium tests. Contains fixes for mac builds, and changes to the google URLs
Create file system tree structure for BOSH plugin development.
Daemons and utility for package and file changes synchronization. Installation requires ruby headers and build tools (make, gcc).
Install, update and remove Vim plugins without changing directories using this simple command line utility.
# Sambot Sambot is our internal Platform Engineering toolchain to help standardize and simplify our DevOps workflow. It provides an executable with a variety of commands, grouped in various areas of functionality such as session management, DNS changes and cookbook management. ## Usage To install the gem, simply run `chef gem install sambot`. This will install the gem in your ChefDK installation. If you want to use it outside Chef, run `gem install sambot`. Run `chef exec sambot` to be shown the help menu. For help on specific commands, i.e. cookbook management and specific cookbook management commands, run `chef exec sambot help cookbook` or `chef exec sambot cookbook help generate` for example. ## Contributing Bug reports and pull requests are welcome on GitHub at https://github.exacttarget.com/ads-devops/sambot. ### Installation Make sure you have `ruby >= 2.4.0` installed. Install `bundler >= 1.15.1` by running `gem install bundler` Run `bundle install` from the root of the project to install the required Ruby gems. ### Running Sambot If you want to test your changes locally, you can run `bundle exec bin/sambot`. ### Running Tests Run `bundle exec rspec spec` to execute the unit tests. Run `cd integration_tests && bundle exec rspec .` to execute the integration tests. These require that you have Docker Compose available. ### Linting There is nothing here yet
Changes the releases' owner to the Wordpress user. Fixes issues where the Wordpress user does not have enough permissions to install or update plugins.
== Jiveapps These tools are all about making Jive App development as easy as possible. After you install the tools, it only takes a single command to: 1. Create a new app - a simple Hello World application. 2. Set up version control for your code using Git. 3. Host the app code online at Jive's AppHosting server. 4. Register the app on the Jive Apps Marketplace as an app "in development". 5. Install the app on your default app dashboard in the Jive Apps Sandbox. After you install, use this simple workflow to make changes and see them reflected in the sandbox: 1. Make a change to the code on your local machine. 2. Commit the changes to your local Git repository. 3. Push the changes to the remote Jive Apps repository. This automatically updates the hosted copy on the Jive AppHosting server. 4. Refresh the app dashboard or canvas page on the Jive Apps Sandbox and see your changes. Other features: * LiveDev: preview your changes on the Jive App Sandbox in real time * Collaboration: add other developers to your project * OAuth Key Management: associate consumer key/secret pairs with service names for use in your apps
Repository for generic common code in Watermark Community Church applications
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.