npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

jthooks

v1.1.0

Published

create a github webhook from the command-line

Downloads

9

Readme

jthooks

Create a github webhook from the command line. Pronounced "ji-thooks", as one would say if pronouncing "githooks" with a soft G, instead of the more common hard-G "gih-thooks".

on npm Tests Coverage Dependencies

Usage

First, create a Github oauth token that has permission to read & write webhooks. Full admin permission is not required. Keep a record of the token somewhere secure.

jthooks [add|remove] user/repo https://example.com/hook shared-sekrit

Commands:
  add <repo> <hook> <secret>  add a hook to the given repo with the shared
                              secret
  remove <repo> <hook>        delete the given webhook; can pass id instead of
                              url

Options:
  --auth, -a   auth token (can also be set in GITHUB_AUTH_TOKEN or
               GITHUB_API_TOKEN)
  --url, -u    full URL of github API to use (optional)
  --quiet, -q  only log errors
  --id         id of existing hook to update (optional)
  --help       show this help                                          [boolean]

Examples:
  jthooks add foo/bar https://example.com/hook sooper-sekrit -a auth-token   add a webhook
  jthooks remove foo/bar https://example.com/hook  remove a hook by url
  jthooks remove foo/bar 123456                    remove a hook by id

If you want to update an existing webhook, run the script with --id. Otherwise the script will attempt to find an existing hook with the same url & update that in place. If no match is found, a hook is created.

Set the --url option if you're not running against github.com but instead wish to change a repo on your Github Enterprise installation.

TODO

Delete a hook.

More than merely cursory tests.

License

ISC; see included LICENSE file.