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

@aritslimited/commitlint

v1.2.0

Published

A commit linting commitizen adapter & branch naming convention tool tailored for ARITS Limited with Jira Issue & Project Tracking Software; to track commits to Jira issues and transition them to the next stage of development workflow automatically.

Downloads

23

Readme

@aritslimited/commitlint

A commit linting commitizen adapter & branch naming convention tool tailored for ARITS Limited with Jira Issue & Project Tracking Software; to track commits to Jira issues and transition them to the next stage of development workflow automatically.

npm (scoped) npm downloads Commitizen friendly Libraries.io dependency status for latest release GitHub Actions/CI GitHub Workflow Status (with event) semantic-release GitHub GitHub repo size GitHub last commit

Table of Contents

Installation

You can install this package via npm or yarn. To install, run the following command:

npm install --save-dev @aritslimited/commitlint commitizen boxen chalk dotenv inquirer node-fetch tslib

or

yarn add -D @aritslimited/commitlint commitizen boxen chalk dotenv inquirer node-fetch tslib

or

pnpm add -D @aritslimited/commitlint commitizen boxen chalk dotenv inquirer node-fetch tslib

or

bun add -D @aritslimited/commitlint commitizen boxen chalk dotenv inquirer node-fetch tslib

Configuration

Run the following command from project root to start using this commitizen adapter along with commitizen:

echo "{\"path\": \"@aritslimited/commitlint/dist/commitlint.config.js\"}" > ./.czrc

Now, you can run the following command to commit your changes:

npx cz

or create a script in your package.json file and use it with npm run commit or yarn commit or pnpm commit or bun commit:

{
  "scripts": {
    "commit": "npx cz"
  }
}

Usage

This package supports the following environment files out of the box:

  • .env
  • .env.local
  • .env.jira.local

Must Have Environment Variables

This package requires the following environment variables to be set in any of the environment files mentioned above that are synced with your version control system (preferably .env):

  • JIRA_BASE_URL=https://aritsltd.atlassian.net/rest/api/2
  • JIRA_PROJECT=your Jira project key # e.g. TAF
  • JIRA_ISSUE_FILTERS=your Jira issue filters # e.g. "In Progress"
  • JIRA_ISSUE_TRANSITION_FILTERS=your Jira issue transition filters # e.g. "Send to QA"

and the following environment variables to be set in any of the environment files mentioned above that are not synced with your version control system (preferably .env.local):

Branch Naming Convention

This package also provides a branch naming convention tool. To use it, include the following environment variables in any of the environment files mentioned above that are synced with your version control system (preferably .env):

  • VALID_BRANCH_NAMES=your string of valid branch names separated by space # e.g. "main staging dev ui"

NB: Branch naming convention tool is optional feature that is disabled by default. To enable it, the VALID_BRANCH_NAMES environment variable(s) must be set.

  • BRANCH_NAME_VALIDATING_REGEXP=your branch name validating regular expression # e.g. "^(main|staging|dev|ui)/[A-Z]{2,3}-[0-9]{1,5}/[a-z0-9-]+$"

BRANCH_NAME_VALIDATING_REGEXP is optional. Default validating regex expression is:

new RegExp(`^(${branchNamesArr.join("|")})[a-z0-9-]*$`)

You can validate your regular expression here.

License

This package is open source and available under the MIT License.

Contributors

| Name | Contact | |----------------------------|----------------------------------------------| | Emran Hossain | GitHub LinkedIn |