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

Hacktoberfest 2026: start here

Open
  • Is something wrong?
#15 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
cloud, typescript
Domain
documentation

Research direction

This is a pinned welcome guide with no specific change to make, so there is no code to locate yet. Read CONTRIBUTING.md, then .nvmrc and src/messages.ts, and run npm install followed by npm run typecheck && npm test to confirm the setup works. To pick up real work, use the unassigned good first issue list linked in the body, and comment there to claim one.

Written by the indexing model from the issue text.

Description

hacktoberfest

Welcome! If you're here for Hacktoberfest, this is the quickest way in. This repo is the CODERCOPS Discord bot: it posts releases, starter issues and merged PRs from our open source repos to Discord, and it serves the leaderboard pages. It's TypeScript on Cloudflare Workers.

Find something to work on

How it works

  1. Comment on the issue you want. I'll assign it to you, usually within a day. Please don't start on one that's assigned to someone else.
  2. One issue at a time. Once you've had 3 PRs merged with us, you can hold two.
  3. Branch off develop, open your PR against develop, and put Closes #<issue number> in the description. The PR has to be opened here in codercops/discord-bot: one merged inside your own fork never reaches us, so it doesn't count.
  4. If there's no PR or update 5 days after you're assigned, I'll free the issue up for someone else. Comment if you need more time.

Setup
You need Node 24 (see .nvmrc). Run npm install, then npm run typecheck && npm test, which is what CI runs. You don't need a Discord server or any tokens: the tests replace Discord, GitHub and KV with fakes, and npm run dev serves the leaderboard page at http://localhost:8787/leaderboard with no secrets. Message text lives in src/messages.ts and has no I/O, so most changes come with a test in test/. See CONTRIBUTING.md.

What counts
PRs count for Hacktoberfest once they're merged or labeled hacktoberfest-accepted. PRs that aren't linked to an issue, only reformat code, or change things nobody asked for get closed, and spam gets the spam label. Have an idea that isn't an issue yet? Open one first so we can agree on it.

AI tools and spam
AI tools are fine, but say so in the PR (the template has an "AI assistance" line) and be ready to explain every line. Untested generated code, a fix split into several PRs, and PRs for issues that aren't assigned to you are treated as spam. Two spam PRs and you won't be assigned more issues this month, and you're out of the goodies. The full rules are in CONTRIBUTING.md.

Goodies
CODERCOPS October 2026 is our own contributor program for this month. The top 5 contributors get a CODERCOPS T-shirt and stickers. You need at least 5 merged PRs labeled hacktoberfest-accepted across chatcops, ogcops, toolbelt and discord-bot, merged between Oct 1 and Oct 31 (UTC). A review can take a day, and changes add another round, so open your PR by Oct 28 to be safe. We still review PRs opened later, but can't promise they get merged by the 31st. Ties go to whoever got there first. The live leaderboard shows where everyone stands, and everyone on it gets a card to share.

These goodies come from CODERCOPS through our own open source program. They're separate from Hacktoberfest, so anything Hacktoberfest itself gives out is a different thing with its own rules. Only PRs for issues that were assigned to you count, and what counts is the maintainers' call.

Questions about anything? Ask right here, or come chat with other contributors on Discord. Claims still happen here on GitHub.

Dominant language
TypeScript
Stars
0
Forks
1
Avg merge
8h 56m
Merged PRs (30d)
53

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.