Send emails when new GitHub Issues are created for a repo
github notify for pull requests
GOV.UK Notify Node.js client
Notify reg-suit result to GitHub repository
A simple SDK for interacting with QAWolf in CI scripts.
Notify reg-suit result to GHE repository using API
GitHub webhook notification service for Zhin.js
gulp plugin to send messages based on Vinyl Files or Errors to Mac OS X, Linux or Windows using the node-notifier module. Fallbacks to Growl or simply logging
A Node.js module for sending notifications on native Mac, Windows (post and pre 8) and Linux (or Growl as fallback)
Postgres pubsub client
Tiny LiveReload server, background-friendly
Communicate important updates to your team via git commit messages
Update notifications for your CLI app
Type-safe search params state manager for React - Like useState, but stored in the URL query string
Sends nyc (aka: istanbul) coverage summary and git build details to Slack using a pass/fail threshold for project coverage.
Es un paquete npm moderno, intuitivo, flexible, liviano e imprescindible para agregar notificaciones emergentes (toasts) a tus aplicaciones web con Next.js.
This is a simple plugin that turns standard Bootstrap alerts into "Growl-like" notifications.
A karma reporter that reports results with OSX Notification Center, Growl or notify-send.
A slack bot for semantic-release notifying release statuses
Post messages in Slack channels when specific Cypress tests and specs fail
Small library that replaces the so-loved jQuery function
Automatic desktop notifications for Grunt errors and warnings. Supports OS X, Windows, Linux.
webpack + node-notifier = build status system notifications
Monkey patches React to notify you about avoidable re-renders.
Easily send comments to GitHub issues
Easy to handle GitHub status with exit status. Like TravisCI's build status.
Octospy notifies events of github repositories to IRC channels.
notify GitHub PR in slack
Be notified of new releases for GitHub, FTP, Docker
Allow your Redmine installation to be notified when changes have been pushed to a Github repository.
notifying your github feed, and push message in Growl.
provide mina deploy, github setup, slack exception notify, i18n scaffold, rails-settings-ui, guard custom
rocket.chat notifier gem, for firing event notifications to a rocket chat incoming webhook. For further information visit the github page: https://github.com/cbajohr/rocketchat-notifier
rocket.chat notifier webhook gem, for firing event notifications to a rocket chat incoming webhook. For further information visit the github page: https://github.com/gleidsonf/rocketchat-notifier.
Keep your eye on new commits being pushed to Github through an interactive interface. When new commits are seen by Hubeye, you can choose to be notified by one of Hubeye's notification systems (growl, libnotify, etc...). All interesting activity is logged, so leave your computer, come back, and know what changed.
ALPHA Alert -- just uploaded initial release. Linux inotify is a means to receive events describing file system activity (create, modify, delete, close, etc). Sinotify was derived from aredridel's package (http://raa.ruby-lang.org/project/ruby-inotify/), with the addition of Paul Boon's tweak for making the event_check thread more polite (see http://www.mindbucket.com/2009/02/24/ruby-daemons-verifying-good-behavior/) In sinotify, the classes Sinotify::PrimNotifier and Sinotify::PrimEvent provide a low level wrapper to inotify, with the ability to establish 'watches' and then listen for inotify events using one of inotify's synchronous event loops, and providing access to the events' masks (see 'man inotify' for details). Sinotify::PrimEvent class adds a little semantic sugar to the event in to the form of 'etypes', which are just ruby symbols that describe the event mask. If the event has a raw mask of (DELETE_SELF & IS_DIR), then the etypes array would be [:delete_self, :is_dir]. In addition to the 'straight' wrapper in inotify, sinotify provides an asynchronous implementation of the 'observer pattern' for notification. In other words, Sinotify::Notifier listens in the background for inotify events, adapting them into instances of Sinotify::Event as they come in and immediately placing them in a concurrent queue, from which they are 'announced' to 'subscribers' of the event. [Sinotify uses the 'cosell' implementation of the Announcements event notification framework, hence the terminology 'subscribe' and 'announce' rather then 'listen' and 'trigger' used in the standard event observer pattern. See the 'cosell' package on github for details.] A variety of 'knobs' are provided for controlling the behavior of the notifier: whether a watch should apply to a single directory or should recurse into subdirectores, how fast it should broadcast queued events, etc (see Sinotify::Notifier, and the example in the synopsis section below). An event 'spy' can also be setup to log all Sinotify::PrimEvents and Sinotify::Events. Sinotify::Event simplifies inotify's muddled event model, sending events only for those files/directories that have changed. That's not to say you can't setup a notifier that recurses into subdirectories, just that any individual event will apply to a single file, and not to its children. Also, event types are identified using words (in the form of ruby :symbols) instead of inotify's event masks. See Sinotify::Event for more explanation. The README for inotify: http://www.kernel.org/pub/linux/kernel/people/rml/inotify/README Selected quotes from the README for inotify: * "Rumor is that the 'd' in 'dnotify' does not stand for 'directory' but for 'suck.'" * "The 'i' in inotify does not stand for 'suck' but for 'inode' -- the logical choice since inotify is inode-based." (The 's' in 'sinotify' does in fact stand for 'suck.')
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.