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

commit-from

v0.7.0

Published

Create a commit message from ticket details from issue sources.

Downloads

21

Readme

commit-from

Create a commit message from ticket details from issue sources.

Why would I use this?

Because:

  • Automate all the things.
  • Save time by rapidly producing commit messages without switching contexts.
  • Enable automated releases by always including necessary metadata.

Currently support issue sources:

  • GitHub
  • Jira

Getting Started

Install node.js 4+.

Install via NPM

npm install -g commit-from

Configuration

Configuration is provided from the .cfconfig file in the user's home directory.

Example

[github]
  issuePrefix = issue-
  template = ~/.gittemplates/github.txt
  timeout = 75000

[jira]
  apiVersion = 2
  host = jira.myhost.org
  password = SprSrsPsswrd1234!@#$
  protocol = https
  strictSSL = true
  template = ~/.gittemplates/jira.txt
  timeout = 75000
  username = someuser

Help

commit-from -h

Git Aliases

# git config file
[alias]
  # current branch name
  current-branch=!git rev-parse --abbrev-ref HEAD
  cb=!git current-branch

  # commit with a message generated from a supported issue source
  commit-from = "!f() { git commit -e -m \"$(CB=$(git cb); if [[ $(dirname "${CB}") = "." ]]; then echo ""; else commit-from $1 $(basename "${CB}") ${@:2}; fi)\"; }; f"
  cf = !git commit-from

  # commit with a message generated from GitHub
  commit-from-github = !git commit-from github
  cfg = !git commit-from-github

  # commit all with a message generated from GitHub
  commit-all-from-github = "!f() { git add -A && git cfg ${@}; }; f"
  cafg = !git commit-all-from-github

  # commit with a message generated from Jira
  commit-from-jira = !git commit-from jira
  cfj = !git commit-from-jira

  # commit all with a message generated from Jira
  commit-all-from-jira = "!f() { git add -A && git cfj ${@}; }; f"
  cafj = !git commit-all-from-jira

Creating a Git Commit

git add <files>
git cfg # From GitHub
git cfj # From Jira

# or commit all the things
git cafg
git cafj

# use a custom template
git cfg -t /path/to/template.txt
git cfj -t /path/to/template.txt