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

git-webhook-ci

v2.0.0-beta

Published

Using git provider webhook to create a poorman CI system

Downloads

25

Readme

git-webhook-ci

A Git (github/gitee) webhook callback server to fetch new code (poor man CI)

This little tool is born out of real projects. Keep having to deploy and setup demo site etc. Why bother if you own the git account? You just need a new cert from github, add this to your project, and setup accordingly, and Viola, you get your own poor man CI :)

Installation

  $ npm install --save git-webhook-ci

or

  $ yarn add git-webhook-ci

Configuration and usage

Create a js file (normally on your project root directory). Let's call it webhook.js.

const gitWebhook = require('git-webhook-ci')
const config = {
  "provider": "github", // from version 2 you MUST provide this
  "secret": "your-github-webhook-secret",
  "path": "/webhook",
  "port": 8081,
  "branch": "refs/heads/master", // New in 0.4.1 you can pass * wildcard to listen to all branches
  "cmd": "git pull origin master --no-edit",
  "error": (err) => {
    // do thing with your error
  }
}

gitWebhook(config)

Full configuration properties

| Property name | Description | Default | Type | | ------------- | ------------- | ---------| -----| | cwd | Where the git root directory is, default to where it gets call | process.cwd() | String | | env | The node environment variable | process.env | Object | | secret | A secret key pass to encrypt data between github and your server | '' | String | | path | The path where the web hook call to your server | /webhook | String | | port | The port number where this callback server running on | 8081 | Integer | | branch | The branch where you will trigger action when received event from github. You can pass * wildcard to listen to all the branches | refs/heads/master | String | | cmd | The command to execute when callback happens. You can also pass this as a function (see above for signature) and especially useful when you use * for branch | git pull origin master --no-edit | String | | error | expect a function and you can handle the error yourself. Or enable DEBUG=git-webhook-ci:error to see the error | () => {} | Function | | inited | only available for wechat provider | false | Boolean |

Debug option

Internally we use debug to track what's going on. So you can just pass the env during the start up of the script to debug your setup.

  DEBUG=* node ./webhook.js

If you do that, you will see a huge amount of info. All our debug flags are prefixed with git-webhook-ci, and here is the list of all the keys we use in this npm.

  • git-webhook-ci:error - This is the most likely you will use, to see the error message
  • git-webhook-ci:main - You will see the configuration option being pass to the main method
  • git-webhook-ci:gitlab
  • git-webhook-ci:github
  • git-webhook-ci:gitee
  • git-webhook-ci:wechat

For example:

  DEBUG=git-webhook-ci:main,git-webhook-ci:error node ./webhook.js

Then you will only see the main (top interface) and the Wechat internal debug messages.

CLI

We drop the cli support since V.2 due to the large amount of configuration options. You can try to write your own follow this example

License

WTFPL - TO1SOURCE / Joel Chu (c) 2021