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

danger-plugin-labels

v2.1.1

Published

Let any contributor (even without write permissions) add labels to their pull requests

Downloads

9

Readme

danger-plugin-labels

Build Status npm version

Let any contributor add labels to their pull requests and issues

Usage

Install:

yarn add danger-plugin-labels --dev

At a glance:

// dangerfile.js
import { schedule } from 'danger'
import labels from 'danger-plugin-labels'

schedule(labels({
  rules: [
    { match: /WIP/i, label: 'Work In Progress' },
    { match: /Ready for Review/i, label: 'Ready for Review' }
  ]
}))
<!-- PULL_REQUEST_TEMPLATE.md -->

**Status (check one)**

- [ ] WIP
- [ ] Ready for Review

Now contributors even without write access to the repo can label their PR as "Work In Progress" and "Ready for Review"!

Note: There is experimental issue support if you're using Peril and point the issue event hook to your Dangerfile. No guarantees it won't break though!

Options

rules (required)

Rules lets you specify which labels to apply depending on which checkboxes are ticked:

schedule(labels({
  // A checked box with "WIP" will apply the "Work In Progress" label
  rules: [{
    match: /WIP/i,
    label: "Work In Progress"
  }]
}))

Because it's tedious to repeat the same string twice if the label matches the checkbox, you can also provide the shorthand notation:

schedule(labels({
  // A checked box with "WIP" will apply the "WIP" label
  rules: ["WIP"]
}))

Note: The checkbox text in this case is case insensitive (wip, Wip and WIP in the markdown would all apply the label), but the label content isn't. (GitHub treats "WIP" as a separate label than "wip", make sure to match the text exactly!)

validate

A function that's called with all the matching labels, allowing you to accept or reject them by returnng true or false, respectively. This is useful for a number of things, for example to limit the maximum number of labels selected:

import { fail } from 'danger';

schedule(labels({
  rules: [/* ... */],
  validate: (labels) => {
    if (labels.length < 1 || labels.length > 3) {
      fail('Please specify at least one and at most 3 labels.');
      return false;
    }

    return true;
  }
}))

This method can also be asynchronous so you can do all sorts of cool stuff, like close issues that users want to label as questions:

import { fail } from 'danger';

schedule(labels({
  rules: [/* ... */],
  validate: async (labels) => {
    if (labels.includes('Question')) {
      fail('Please direct questions to the community on Spectrum.')
      await closeIssue();
      return false;
    }
    return true;
  }
}))

Changelog

See the GitHub release history.

Contributing

See CONTRIBUTING.md.