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

pending-pr

v0.2.0

Published

pending-pr handles pending pull requests

Downloads

14

Readme

pending-pr Build Status

pending-pr is a CLI tool which handles pending pull requests.

Motivation

In a recent project, We had 500 pull requests in a month, with scattered repositories. If repository is only one or two, it's not a problem. But we had API, client, and plugins, and lots of others. That's why I created pending-pr, it's a small cli tool focusing only pending pull requests.

Getting Started

Install the module with:

$ npm install -g pending-pr

Create .pending-pr file with init command:

$ pending-pr init
Token: YOUR_GITHUB_OAUTH_TOKEN
Repos: foo/bar baz/qux
Members: banyan foo bar
24 Sep 00:55:20 - info: create /Users/banyan/tmp/pending-pr/.pending-pr

$ cat .pending-pr
{
    "token": "YOUR_GITHUB_OAUTH_TOKEN",
    "repos": ["foo/baz", "baz/qux"],
    "members": ["banyan", "foo", "bar"]
}
  • token is your github oauth token.
  • repos is that you'd like to check if they have pending PRs.
  • members is that you'd like to mention to them.

Usage

Commands:

    init                 Create .pending-pr config file.
    list                 Show mergeble pull requests. Short-cut: l
    count                Show mergeble pull requests size. Short-cut: c
    ping                 Ping to pull request to be merged. Short-cut: p
    open                 Browse pull request. Short-cut: o

Tips

With Jenkins or cron, it can be checked whether pending PRs exists and notify regulary.

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Running the Tests

$ grunt test

TODO

  • Customizable message
  • Configurable of unmergeble keywords

License

Copyright (c) 2013 Kohei Hasegawa Licensed under the MIT license.