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-api

v0.0.1

Published

Git Webhook API Project

Downloads

4

Readme

git-webhooks

Getting Started

GitLab local instance

You can install GitLab Community Edition for testing purposes.

First, install Docker.

Second, create a docker volume for persistent data : docker volume create vol-gitlab.

Then, you can simply run :

docker run --detach \
	--hostname gitlab.example.com \
	--publish 443:443 --publish 80:80 --publish 22:22 \
	--name gitlab \
	--mount source=vol-gitlab,target=/app \
	--restart always \
	--volume /srv/gitlab/config:/etc/gitlab \
	--volume /srv/gitlab/logs:/var/log/gitlab \
	--volume /srv/gitlab/data:/var/opt/gitlab \
	gitlab/gitlab-ce:latest

Or, for Windows PowerShell : docker run --detach --hostname gitlab.example.com --publish 443:443 --publish 80:80 --publish 22:22 --name gitlab --mount source=vol-gitlab,target=/app --restart always --volume /srv/gitlab/config:/etc/gitlab --volume /srv/gitlab/logs:/var/log/gitlab --volume /srv/gitlab/data:/var/opt/gitlab gitlab/gitlab-ce:latest

Tip : do not use Windows PowerShell ISE

Docker instance

You can create a docker image of our Webhook Project running this script :

docker build -t my-webhook .

Then, you can simply run a container :

docker run --name webhook-container -d -p 3000:3000 my-webhook:latest

Finally, you can configure the webhook attachs to your git repository with the url : http://localhost:3000/webhook.

Tip : you can use ngrok to convert localhost url to public url.

Customisable Rules

You can customise the existing rules, by adding yours. Rules are quiet simply to extend. They are in this rules.yml file, located in src/rules/rules.yml and must respect the Rule class (src/rules/rule.class.ts).

Example:

- name: commitMessage
  enabled: true
  events:
    - Push
  options:
    regexp: (feat|fix|docs)\(?[a-z]*\)?:\s.*
  onSuccess:
    - callback: logger.info
      args:
        - 'pattern match'
        - 'good game'
    - callback: logger.info
      args:
        - 'another action is being executed'
        - 'commit will successed'
  onError:
    - callback: logger.warn
      args:
        - 'pattern does not match'
        - 'commit name must begin with : "feat|fix|docs"!'
    - callback: logger.warn
      args:
        - 'another action is being executed'
        - 'commit will fail'

If you want to create a new type of rule, you must create your own class. It must extend the abstract Rule class, and implement the valide() function. This function contains all your business logic.

You can have a look at the CommitMessageRule.ts class located in src/rules.