github-webhook-handler - GitLite

KO | EN

gitlite — search

#javascript #python #hacktoberfest #ai #typescript #llm #machine-learning #deep-learning #docker #macos #java #kubernetes #security #open-source

github-webhook-handler

(★ 793)

Node.js web handler / middleware for processing GitHub Webhooks

File Explorer

Download Latest Version (.zip)

- - depsound.yml
  - test-and-release.yml
- dependabot.yml
- github-webhook-handler.d.ts
- github-webhook-handler.d.ts.map
.gitignore
CHANGELOG.md
events.json
github-webhook-handler.js
LICENSE.md
package.json
README.md
test.js
tsconfig.json

🚀 Installation Guide

1. Get the code

git clone https://github.com/rvagg/github-webhook-handler

Downloads the entire project code from GitHub to your computer.

cd github-webhook-handler

Moves into the project folder you just downloaded.

2. Node.js

Easy Recommended

Prerequisites

Git Needed to download the project code from GitHub.
Node.js Node.js must be installed to use npm. The LTS version is recommended.

npm install

Downloads and installs the libraries listed in package.json.

npm start

Starts the development/run server.

✅ After running the command, open the address shown in the terminal (usually something like http://localhost:3000) in your browser.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# github-webhook-handler

[![NPM](https://nodei.co/npm/github-webhook-handler.svg?style=flat&data=n,v&color=blue)](https://nodei.co/npm/github-webhook-handler/)

GitHub allows you to register **[Webhooks](https://developer.github.com/webhooks/)** for your repositories. Each time an event occurs on your repository, whether it be pushing code, filling issues or creating pull requests, the webhook address you register can be configured to be pinged with details.

This library is a small handler (or "middleware" if you must) for Node.js web servers that handles all the logic of receiving and verifying webhook requests from GitHub.

## Requirements

Node.js >= 20

## Tips

In Github Webhooks settings, Content type must be `application/json`.

`application/x-www-form-urlencoded` won't work at present.

## Example

```js
import http from 'node:http'
import createHandler from 'github-webhook-handler'

const handler = createHandler({ path: '/webhook', secret: 'myhashsecret' })

http.createServer((req, res) => {
  handler(req, res, (err) => {
    res.statusCode = 404
    res.end('no such location')
  })
}).listen(7777)

handler.on('error', (err) => {
  console.error('Error:', err.message)
})

handler.on('push', (event) => {
  console.log('Received a push event for %s to %s',
    event.payload.repository.name,
    event.payload.ref)
})

handler.on('issues', (event) => {
  console.log('Received an issue event for %s action=%s: #%d %s',
    event.payload.repository.name,
    event.payload.action,
    event.payload.issue.number,
    event.payload.issue.title)
})
```

For multiple handlers, see [multiple-handlers-issue](https://github.com/rvagg/github-webhook-handler/pull/22#issuecomment-274301907).

## API

github-webhook-handler exports a single function. Use this function to *create* a webhook handler by passing in an *options* object. Your options object should contain:

* `"path"`: the complete case sensitive path/route to match when looking at `req.url` for incoming requests. Any request not matching this path will cause the callback function to the handler to be called (sometimes called the `next` handler).
 * `"secret"`: this is a hash key used for creating the SHA-1 HMAC signature of the JSON blob sent by GitHub. You should register the same secret key with GitHub. Any request not delivering a `X-Hub-Signature` that matches the signature generated using this key against the blob will be rejected and cause an `'error'` event (also the callback will be called with an `Error` object).
 * `"events"`: an optional array of whitelisted event types (see: *events.json*). If defined, any incoming request whose `X-Github-Event` can't be found in the whitelist will be rejected. If only a single event type is acceptable, this option can also be a string.

The resulting **handler** function acts like a common "middleware" handler that you can insert into a processing chain. It takes `request`, `response`, and `callback` arguments. The `callback` is not called if the request is successfully handled, otherwise it is called either with an `Error` or no arguments.

The **handler** function is also an `EventEmitter` that you can register to listen to any of the GitHub event types. Note you can be specific in your GitHub configuration about which events you wish to receive, or you can send them all. Note that the `"error"` event will be liberally used, even if someone tries the end-point and they can't generate a proper signature, so you should at least register a listener for it or it will throw.

See the [GitHub Webhooks documentation](https://developer.github.com/webhooks/) for more details on the events you can receive.

Included in the distribution is an *events.json* file which maps the event names to descriptions taken from the API:

```js
import events from 'github-webhook-handler/events.json' with { type: 'json' }

for (const [event, description] of Object.entries(events)) {
  console.log(event, '=', description)
}
```

Additionally, there is a special `'*'` event you can listen to in order to receive _everything_.

## License

**github-webhook-handler** is Copyright (c) 2014 Rod Vagg and licensed under the MIT License. All rights not explicitly granted in the MIT License are reserved. See the included [LICENSE.md](./LICENSE.md) file for more details.