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

grev

v1.0.10

Published

This tool exists to simplify the review process at RB.

Downloads

15

Readme

Grev

Grev Screencast

Grev (gee-rev, short for git review) is a command line utility that streamlines the process of submitting a code review at Recovery Brands. It integrates with JIRA, GitHub, and Slack to transition JIRA task statuses, open a GitHub PR, and notify peer code-reviewers in Slack. Additionally, it contains conveinence features like automatically inserting the JIRA task link in the GitHub PR body and inserting the GitHub PR link in the JIRA task's comment section. Grev works by utilizing each of the previously mentioned services' APIs with the help of InquirerJS for collecting input from the user.

How It Works

As of right now, grev is only designed to work for Recovery Brands. You can fork this repo and edit config.js to make it work for your own company. You will also need to make sure your JIRA transition IDs are configured accordingly.

grev uses Inquirer.js to prompt the user for input and perform the following actions:

  1. Prompts the user for whether they would like to submit a pull-request (PR) to the source repo or a fork (gets available forks via GitHub API).
  2. Prompts the user for the base branch (gets available branches via GitHub API).
  3. Opens up browser to allow for code changes to be reviewed against base branch.
  4. Prompts user for whether or not they would like to proceed after viewing changes. If yes, grev continues. If no, grev exits.
  5. Opens up user's default code editor (as configured in next section) so they can enter PR body (in markdown format) for GitHub. The code editor will already have inserted a link to the JIRA task for convenience. grev will continue once code editor is closed.
  6. Submits the PR to GitHub and posts the PR link in both the terminal window and as a comment in the JIRA task.
  7. Prompts the user for whether they would like to transition the JIRA task status to In Review.
  8. Prompts the user for which co-workers in Slack they would like to notifiy about the PR (pulls users via Slack API).
  9. Posts a link to the GitHub PR in the frontend-prs Slack channel and tags the users specified in the previous step.

Installation and Use

Initial Configuration

Before you can run the tool, you'll need to make sure you have the following entries added to your global .gitconfig file (should be located @ /Users/USERNAME/.gitconfig):

[github]
    key = YOUR_GITHUB_API_KEY
    self = YOUR_GITHUB_USERNAME
[jira]
    key = YOUR_JIRA_API_KEY
    self = YOUR_JIRA_USERNAME
    url = RECOVERY_BRANDS_JIRA_URL
[slack]
    key = YOUR_SLACK_API_KEY
[core]
    editor = code --wait

Installation

Grev should be installed as a global npm package:

npm install -g grev

or

yarn global add grev

Use

Make sure your terminal is in one of our site's working directory:

.../wp-content/themes/superThemev3/

Make sure your branch name is the JIRA task you are working on:

FE-192

After you've committed and pushed your last changes to GitHub, run the following command:

grev