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

missed-issues

v1.0.0

Published

Find all issues in a github org that mention a team by have not be replied to by the team members

Downloads

4

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

mcwhittemoremcwhittemore

Keywords

githuborgticketsissues

Readme

Missed Issues

A CLI tool for finding issues that mention a team and no one from the team has responded to the issue.

This will list all issues in the mapbox org that mention @mapbox/teamname where no member of that team has replied to the issue since the mention.

> missed-issues --org mapbox --team teamname --token github_token

Possible output

## check-file-dependencies

- [ ] [#1123 - Consider evaluating expressions](https://github.com/mapbox/check-file-dependencies/issues/new)

## missed-issues

- [ ] [#42 - Document the node module interface](https://github.com/mapbox/missed-issues/issues/new)

Flags

Required

  • --org: the name of the org you want to search.
  • --team: the name of the team you are checking into. This MUST not contain the name of the org.
  • --token: a GitHub token with read:org, repo access

Optional

  • --from: the start date of your search range. All issues returned will have been edited on or after this date. Defaults to one week ago. from must either be a YYYY-MM-DD string such as 2017-11-16 or a ###d string suck as 21d. The ###d format allows for "days from now".
  • --ignore-repos a comma-separated list with no spaces of repos that you wish to exclude from your search results. These are excluding via filtering and will thus still affect your max-issues number. (eg: missed-issues,mapbox-gl-draw).
  • --max-issues: the max number of issues to get before filtering to help avoid long requests. Defaults to 100. That said, hitting this max is bad for your results.
  • --nonmembers: a comma-separated list of user logins who should not be used to count a ticket as replied too.

Environment Variables

missed-issues allows you to use environment variables to set unprovided flags. This is very helpful if you are running this for a single team or a single org and it lets you not paste your GitHub token into your terminal over and over again.

Below is a list of env vars missed-issues supports. The value of the env var is the flag the key will set.

GITHUB_TOKEN=token
MISSED_ISSUES_ORG=org
MISSED_ISSUES_TEAM=team
MISSED_ISSUES_IGNORE_REPOS=ignore-repos
MISSED_ISSUES_NON_MEMBERS=nonmembers

.env files

If you have a .env file in the folder returned by which missed-issues then missed-issues will auto load these env vars on every run.