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

fixdiscover

v1.2.0

Published

Small CLI tool to search for Jira issues with linked PRs and Issues that are fixed in an upstream projects.

Downloads

87

Readme

JIRA FixDiscover

npm version Tests Linters CodeQL codecov

Description

Small CLI tool to search for Jira issues with linked PRs and Issues that are fixed in an upstream projects.

Usage

Make sure to store your JIRA Personal Access Token (PAT) and GitHub PAT in the ~/.config/fixdiscover/.env or ~/.env.fixdiscover file:

# ~/.config/fixdiscover/.env
JIRA_API_TOKEN="exaple-token"
GITHUB_API_TOKEN="exaple-token"

[!TIP]

You can also set default values for the component and upstream in the ~/.config/fixdiscover/.env or ~/.env.fixdiscover file:

# ~/.config/storypointer/.env
COMPONENT="your-component"
UPSTREAM="upstream-project"

Using Node.js

# run it using npx
npx fixdiscover

# or install it globally using npm
npm install -g fixdiscover
fixdiscover

How to use

[!IMPORTANT]

This tool is intended to be used by Red Hat employees on the Red Hat JIRA instance. It may be adapted to work with other JIRA instances in the future.

$ fixdiscover --help
Usage: fixdiscover [options]

🔍 A small CLI tool is used to search for Jira issues with linked PRs and issues that are fixed in upstream projects

Options:
  -V, --version                output the version number
  -c, --component [component]  issue component
  -u, --upstream [upstream]    upstream project
  --migrate                    migrate links from Bugzilla to Jira
  -n, --nocolor                disable color output (default: false)
  -x, --dry                    dry run (default: false)
  -h, --help                   display help for command

[!TIP]

You can disable color output by setting the NOCOLOR environment variable to true.

NOCOLOR=true npx fixdiscover

Similarly, you can enable dry run by setting the DRY environment variable to true.

Examples

Size all issues of the curl component:

fixdiscover -c systemd -u systemd/systemd

https://issues.redhat.com/browse/RHEL-66198
  - commit: https://github.com/systemd/systemd/commit/7102dc52e6b03248da1f01b3a8a4b83c6d7a1316
  - commit: https://github.com/systemd/systemd/commit/d25a9bfa8f8bd42b769dbf2f9786348864cf5e08
  - commit: https://github.com/systemd/systemd/commit/67f90b0d85bc425ec2c11106e8270c981c36585a
  - commit: https://github.com/systemd/systemd/commit/3d689b675b565c29a51c7127ae30839987aaa18b

https://issues.redhat.com/browse/RHEL-50103
  - issues: https://github.com/systemd/systemd/issues/34082
  - pull: https://github.com/systemd/systemd/pull/34099
  - pull: https://github.com/systemd/systemd/pull/33682