Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Leaderboard page: name the people who qualify but haven't linked their GitHub yet

Open
  • Is something wrong?
#55 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@varun-pahuja is already working on this.

Since Oct 20, 2026.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
76/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
backend-api-design, frontend

Research direction

Read handleLeaderboardPage in src/index.ts, linkedMembers in src/links.ts, and the page and message helpers in src/page.ts and src/messages.ts; compare the existing linking tests in test/page.test.ts and route tests in test/index.test.ts. Follow the acceptance criteria for qualifying rows, program end, lookup failures, escaping, and phone width. Done means the line appears only for qualifying unlinked people, the page remains available after lookup errors, and the requested tests pass.

Written by the indexing model from the issue text.

Description

enhancement hacktoberfest help wanted

We contact the winners by Discord DM, so we need to know which Discord account goes with each GitHub login, and we only know that once the person has run /link (src/links.ts). The leaderboard page has one general line about it near the bottom (src/page.ts, line 195), but it doesn't say who still has to do it. Two of the six people who qualify on the October board haven't linked yet.

The final results post in Discord already names the winners who haven't linked (leaderboardMessage in src/messages.ts, lines 161 to 165). The page should do the same while there's still time.

What to do

  • In handleLeaderboardPage (src/index.ts, line 105), when linking is on (linkingEnabled(env)), check who has linked with linkedMembers (src/links.ts, line 46). Only pass the logins of the rows that qualify: it's one KV read per login, and there's no reason to read the whole board.
  • Pass the result to leaderboardPage and add one line above the board that names the people who qualify but haven't linked, for example: "octocat and hubot qualify but haven't linked their GitHub yet. Join the Discord and run /link there, so we can reach you if you win." Link each name to the person's GitHub profile like the rows do, and "Join the Discord" to links.discord.
  • Once the program has ended, name only the winners (row.winner), like the final results post does.
  • Add nothing when linking is off, when nobody qualifies yet, or when everyone who qualifies has linked.
  • If the lookup fails, log it and show the page without the line. Right now any error in handleLeaderboardPage turns the whole page into a 503 (line 137).
  • Chips are hidden on narrow screens (src/page.ts, line 124), so don't make it a chip. It has to show on a phone.
  • Leave the JSON (/leaderboard/{id}.json) as it is.

Where to look

  • src/index.ts: handleLeaderboardPage (line 105), and the final results post, which calls linkedMembers (line 361)
  • src/links.ts: linkedMembers (line 46) gives a map from the lowercased login to the Discord id, for the logins that are linked
  • src/page.ts: leaderboardPage (line 137), the status line (line 188) and the Discord note (line 195)
  • src/messages.ts: joinNames (line 86) and the sentence about unlinked winners (line 164)
  • test/page.test.ts: the linking tests (line 89), and test/index.test.ts for the route (makeEnv in test/helpers.ts comes with an in-memory KV)

#4 changes the rows of the same page and #38 changes its <head>, so keep this to the new line and the lookup.

Acceptance criteria

  • With linking on, the line names everyone who qualifies and hasn't linked, in board order, with links to their GitHub profiles, and nobody who has linked
  • After the end, only winners who haven't linked are named
  • No line when linking is off, when nobody qualifies, or when everyone who qualifies has linked
  • Only qualifying rows are looked up, and a failed lookup still shows the page, without the line
  • Logins are escaped, since they come from GitHub
  • The line shows at phone width
  • Tests for the cases above, for the page and for the route
  • A screenshot of the page with the line, in the PR
  • npm run typecheck and npm test pass

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 #55 in the description.

Dominant language
TypeScript
Stars
0
Forks
1
Avg merge
14h 21m
Merged PRs (30d)
30

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from codercops/discord-bot

All issues in codercops/discord-bot

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.