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

prefix-commit-message

v4.2.0

Published

Git hook to extract ID from branch name into commit message

Downloads

6,744

Readme

Prefix Commit Message

This script is meant to be used as a prepare-commit-msg Git hook. Each time you commit, it extracts the issue identifier or user-story identifier from the current branch name and prefixes your commit message with the extracted identifier.

It supports identifiers of the form ABCD-1234 and 1234, and will look for such identifiers right after the / in the name of the current branch. If you're on the branch feature/JIRA-874-cannot-log-in-on-macos, for example, this hook will prefix each of your commit messages with [ JIRA-874 ] .

There are simpler shell scripts that achieve the same, but this solution works on Windows too.

This script can be used standalone or in combination with Husky (version 6 and newer). If you're using an older Husky, see (https://github.com/ljpengelen/prefix-commit-message/tree/v1.3.0).

Installation

Standalone usage

Navigate to .git/hooks from the root of your Git repository and create an executable file named prepare-commit-msg with the following content:

#!/bin/sh
npx prefix-commit-message $1

Usage with Husky

First, install Husky and this script:

npm install husky --save-dev
npm install prefix-commit-message --save-dev

Then, enable Git hooks via Husky:

npx husky install

Finally, set up the prepare-commit-msg hook:

npx husky add .husky/prepare-commit-msg "npx prefix-commit-message \$1"

Custom prefix

If you don't like the square brackets around the identifier, you can supply a custom opening and closing symbol. For example,

#!/bin/sh
npx prefix-commit-message $1 -o -c :

and

npx husky add .husky/prepare-commit-msg "npx prefix-commit-message \$1 -o -c :"

will result in the prefix JIRA-874: .

The opening symbol is specified via the '-o' flag, and the closing symbol is specified via the '-c' flag. As the example shows, the empty string is used when no value is specified after a flag.

Including and excluding branches

If you want to apply the hook to specific branches only, you can supply a regex pattern for branches to include and exclude. For example,

#!/bin/sh
npx prefix-commit-message $1 -bi ^feature -be release

and

npx husky add .husky/prepare-commit-msg "npx prefix-commit-message \$1 -bi ^feature -be release"

will only extract the identifier from branches that start with the string "feature" and do not contain the string "release".

The pattern for branches to include is specified via the '-bi' flag, and the pattern for branches to exclude is specified via the '-be' flag.