`/issues` and "Find an issue" link to blocked issues the bot leaves out
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, typescript
- Domain
- backend, developer-experience
Research direction
Read listUrl in src/messages.ts and ISSUES_URL in wrangler.jsonc; compare their search filters with the blocked issue exclusion in src/github.ts. Update both links to exclude blocked issues, then add assertions in the starterIssuesReply tests in test/messages.test.ts for the links. Done when both links exclude blocked issues and npm run typecheck and npm test pass.
Written by the indexing model from the issue text.
Description
/issues lists open, unassigned starter issues and skips anything labeled blocked (listStarterIssues in src/github.ts, line 99). The links in its reply don't: the embed title and "and N more" both use listUrl (src/messages.ts, line 193), and that search has no -label:blocked. For toolbelt today, the bot lists 6 issues and the link opens 11: the same 6 plus #36, #37, #38, #39 and #41, which are all blocked.
The "Find an issue" link has the same gap. ISSUES_URL (wrangler.jsonc, line 85) is used on the leaderboard page, the contributor pages and the welcome post (src/index.ts, lines 126 and 309, and src/welcome.ts, line 59), and it matches toolbelt #41, which is blocked.
What to do
- Add
-label:blockedto the search inlistUrl. - Add
-label:blockedtoISSUES_URL.
Where to look
src/messages.ts:starterIssuesReply(line 184) andlistUrl(line 193)src/github.ts:listStarterIssues(line 85)wrangler.jsonc:ISSUES_URL(line 85)test/messages.test.ts: thestarterIssuesReplytests (line 207) check the link withtoContain, so add a check for-label:blockedthere
Acceptance criteria
- The
/issuestitle link and the "and N more" link leave out blocked issues, so they open the same issues the bot lists -
ISSUES_URLleaves out blocked issues - Tests for both links
-
npm run typecheckandnpm testpass
Want to work on this? Comment below and I'll assign it to you. Please take one issue at a time, branch off develop, and open your PR against develop with Closes #57 in the description.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 14h 21m
- Merged PRs (30d)
- 30
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from codercops/discord-bot
-
bug good first issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
codercops/discord-bot#58 ·
Maintainers usually reply within 1 day
-
bug good first issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
codercops/discord-bot#56 ·
Maintainers usually reply within 1 day
-
bug hacktoberfest help wanted
Difficulty 4/5 3-5 days Newbie friendliness 48/100
codercops/discord-bot#59 ·
Maintainers usually reply within 1 day
-
Leaderboard page: name the people who qualify but haven't linked their GitHub yetPossibly taken @varun-pahuja claimed this today. Openenhancement hacktoberfest help wanted
Difficulty 3/5 1-2 days Newbie friendliness 76/100
codercops/discord-bot#55 · 1 comment ·
Maintainers usually reply within 1 day
-
hacktoberfest
Difficulty 1/5 Under an hour Newbie friendliness 15/100
codercops/discord-bot#15 ·
Maintainers usually reply within 1 day
All issues in codercops/discord-bot
Similar issues
-
area:editor bug issue-form:bug P0 platform:windows review: low
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
1lck/Lithe-IDEA#1388 ·
Maintainers usually reply within 1 day
-
fix(api): isToolAuditEnabled swallows database read errors on auditToolOperations without loggingOpenarea: backend bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
snapotter-hq/SnapOtter#3238 ·
Maintainers usually reply within 1 day
-
rig up --plan times out after 5 s and reports an UNKNOWN outcome while the daemon completes the planOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/servers#5216 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day