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

joyent-grr

v1.8.0

Published

A 'grr' CLI tool to help use Joyent's CR tool, Gerrit (https://cr.joyent.us)

Downloads

68

Readme

This repo provides a single grr CLI tool to help with using Joyent's code review (CR) tool, Gerrit, at: https://cr.joyent.us/.

Grr is opinionated. The expected workflow is this:

  1. You call grr <issue> to tell grr to create a temporary local branch (grr-<issue>) for work on this issue (if you are currently on "master"), or to use your current branch (if you are already on a non-"master" branch). Grr will fetch issue details and remember them (in local git config). Optionally you can specify "extra issues" that your changes cover, via grr -a <extra-issue>. Those issues will be included in the commit message.
  2. You make one or more commits, git commit -am ..., for your change.
  3. You call grr to create/update the CR. Grr will squash the commits (in a temporary grr/auto/<issue> branch), push the commit (with the appropriate commit message) to cr.joyent.us, and remember the CR number.
  4. Get approvals for your CR, and/or cycle back to step #2.
  5. When you get approval, run grr one last time to update the commit message with "Reviewed by" and "Approved by" lines.
  6. Integrate your change (in the web UI, grr doesn't yet do this), then use grr -D to clean up (delete the grr-<issue> branch and switch back to master).

See this example for a walk through.

Install

npm install -g joyent-grr

Verify that it is installed and on your PATH:

$ grr --version
grr 1.2.0
https://github.com/joyent/grr

You'll need to setup your account in Joyent's Gerrit by following the steps at https://github.com/joyent/joyent-gerrit/blob/master/docs/user/README.md#new-user-instructions

Development Hooks

Before commiting be sure to, at least:

make check      # lint and style checks
make test       # run tests

A good way to do that is to install the stock pre-commit hook in your clone via:

make git-hooks

License

MPL 2.0