cutenode / cutenode/good-first-issue

Error with 'docusaurus': output issues aren't always from docusaurus

Open
#193 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
832
Forks
236
PR merge metrics
No merged PRs in 30d

Description

When running `npx good-first-issue docusaurus`, the outputs can be from other projects. For example here it outputs issues of jest:

![docusaurus](https://user-images.githubusercontent.com/35877936/83572647-7857b200-a519-11ea-9f59-7ff640c2d92f.png)

I checked in `data/projects.json` and the query for docusaurus seems wrong:
```
"docusaurus": {
"name": "Docusaurus",
"q": "org:facebook is:issue is:open label:\"good first issue\"",
"description": "Easy to maintain open source documentation websites. "
},
```

I tried changing it to a query to the repo:
```
"docusaurus": {
"name": "Docusaurus",
"q": "repo:facebook/docusaurus is:issue is:open label:\"good first issue\"",
"description": "Easy to maintain open source documentation websites. "
},
```

But running `npx good-first-issue docusaurus` still outputs other projects.

What else could I do to try and fix this?

Contributor guide

Open the contributing guide

Research direction

Start with data/projects.json and the code behind `npx good-first-issue docusaurus`, then reproduce the command to inspect how its query is used. Verify that the output contains only open good-first-issue issues from facebook/docusaurus, and add or update coverage if the repository has relevant tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, javascript
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.