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

stash-creview

v1.2.1

Published

CLI for creating pull requests with random reviewers in Atlassian Stash

Downloads

20

Readme

stash-pullrequest

Pull Request CLI for Atlassian Stash

Install

npm install stash-creview -g

Config

You will need to specify the following environment variables in ~/.profile, ~/.bashrc, or some other file that is loaded when you open your terminal of choice:

...
export STASH_CREVIEW_PROTOCOL=http
export STASH_CREVIEW_HOST=stash.company.com
export STASH_CREVIEW_PORT=7990 # this is the default port for stash
export STASH_CREVIEW_USERNAME=username
export STASH_CREVIEW_PASSWORD=password
export STASH_CREVIEW_STATIC_REVIEWERS=bob,bill # OPTIONAL
...

You will also need to put a config file (.creview-config) in the root of every repo that this program will be used for. Here is a sample one:

{
    /* these denote 'sections' of your repo */
    "sections": [
        {
            /*
             * so either bobby or billy can be used as reviewers for 
             * code that is in the 'API' section of the repo
             */
            "key": "API",
            "groupSlug": "stash-group-slug-api"
        },
        {
            "key": "UI",
            "groupSlug": "stash-group-slug-ui"
        },
        {
            "key": "QA",
            "groupSlug": "stash-group-slug-qa"
        }
    ],
    "parseBranchRegex": "TICK-\d\d\d\d", /* regex to auto-determine the ticket number */
    "projectKey": "FOOB",
    "slug": "repo1" /* repo slug. should be the same as the repo name */
}

For each "groupSlug" specified in the .creview-config file, you will need a Stash group by that name. It should contain all of the users that could possibly perform a review for that type of pull request.

Usage

creview --help # get help to see all documentation
cd path/to/repo
cd even/deeper # it doesn't matter, where you are in the repo. We'll find the root for you :)
creview -t TICK-1234 -m "Im making a pull request." -s UI # make a pull request that involves only UI code changes

Notes

  • this only supports up to 1000 users per group. We could add support for more, but I didn't feel like dealing with paging api's right now.
  • the "-s" and "--sections" parameters are no longer required.
  • the STASH_CREVIEW_STATIC_REVIEWERS env var will limit your random reviewers. A static reviewer CANNOT be one of the randomly selected reviewers.
  • the parseBranchRegex .creview-config value will always be run in a case-insensitive context, and only return the first match