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

jira-precommit-hook

v4.0.0

Published

Git commit hook to verify commit messages are tagged with a JIRA issue number

Downloads

15

Readme

jira-precommit-hook

Goals:

  • Commit hook script contains the bare bones needed to call into this library. We may want to investigate use of existing pre-commit module.

NOTICE

Currently only configured for read-only access to JIRA.

Project Configuration

DESCRIPTION

In order to communicate with your JIRA server, a .jirarc file needs to be placed in the root of the repo.

{
	"projectName": "<Name of JIRA project - REQUIRED>",
	"host":"<URL location of JIRA project - REQUIRED>",
	"protocol":"[default:http|https]",
	"port": default:80,
	"version": default:2,
	"verbose": default:false,
	"strictSSL": default:true
}

INSTALLATION

To install, run the following with npm:

> npm install jira-precommit-hook

SYMLINK DIRECTORY NOTICE

If the hooks directory in your .git folder is symlinked, the module will be unable to find it. To avoid this, do not symlink your hooks folder inside of your project's git directory.

Making JIRA Commits

In order to make a successful commit with the precommit hook, ALL issues being committed must meet the following requirements:

  • There must be at least one issue in the commit message
  • All committed issues must exist in the project designated in the .jirarc

At least one issue being committed must meet the following requirements:

  • The issue must be open for commits
  • The parents of the issue must also be open for commits
    • The issue must lead up to an initiative
  • The issue must not be an initiative, epic, nor a deployment task

Jokes

By default you will get a joke presented to you upon a successful commit. This is two-fold, first to get you accustomed to the commit hook so you are aware when it's not present. The second is for some comic relief at work, cause we all need it.

To disable the jokes from your shell

> ./node_modules/.bin/jira-precommit jokes disable

To re-enable the jokes from your shell

> ./node_modules/.bin/jira-precommit jokes enable

To disable To disable the joke feature simply delete the .chuckNorris file from your home directory.