Hacktoberfest 2026: Pull Requests No Longer Count

Hacktoberfest 2026 is live now, and it is not the Hacktoberfest you remember. Pull requests no longer count toward rewards. That single change turns October’s best-known open-source event from a numbers exercise into something closer to a build-and-learn programme, and it means the strategy that worked for the last nine years will not work this year.

The event runs through October, is free, and is open to anyone anywhere. Participation now centres on contributing to open-source AI and open-weight projects rather than accumulating merged pull requests. Individual Fests run as one-day in-person events worldwide, with a global online track alongside them. The official site is hacktoberfest.com — register there, because the dashboard opened on 1 October and that is where the participation tracking now lives.

Key facts

What	Month-long open-source celebration, run throughout October
Who runs it	MLH and DEV, presented by DigitalOcean
Cost	Free
Eligibility	Open to anyone, anywhere. No student requirement
Format	300+ one-day in-person Fests worldwide, plus a global online track with livestreams, mini-challenges and Global Hack Week
Rewards	Virtual stickers for participating; a physical sticker pack is mailed
Registration	Participant dashboard opened 1 October 2026
Official site	hacktoberfest.com

All details from the official Hacktoberfest site. Deadline: none, because it is an event that runs all month rather than an application.

Table of Contents

What actually changed

For nine years the deal was simple: get four merged pull requests accepted and you had earned Hacktoberfest. Maintainers noticed, and the event became partly a measurement of who could farm trivial contributions. This year merged pull requests are not the reward metric.

The event is now oriented around open-source AI and open-weight projects, with participation tracked through the dashboard rather than through your commit history. That has three practical consequences for you if you were planning to enter.

Do not aim for a pull-request count. It is not what is being measured, and a repository accepting cosmetic changes is doing so for the wrong reason.
Pick a substantive target early. Something you can actually test, document or fix. The projects that benefit from October attention are the ones with real open issues in AI tooling, model weights, and inference infrastructure.
Read the project’s contributing guide before you touch anything. This was always good manners. It is now the difference between a contribution that gets merged and one that gets closed.

Doing it well: a realistic October plan

If your goal is a portfolio piece that survives someone asking about it in an interview, aim for one of these rather than a spread of trivial merges.

Fix a real bug with a reproduction. The issue thread, the failing case and the fix tell a better story than any number of merged diffs. There is a direct overlap here with automated fuzzing workflows for finding exactly those bugs.
Improve documentation or examples. Underrated, still needed, and a good way to learn an unfamiliar codebase properly.
Add a test that would have caught a past bug. Concrete, reviewable, and permanently valuable.
Contribute to an open-weight model’s tooling — evaluation harnesses, dataset scripts, inference utilities — rather than the model itself, where the barriers to a useful contribution are much higher.
Triage. Issues that reproduce, with versions and environment details, are genuinely valuable and almost always welcomed.

Choosing between a local Fest and the online track

With 300-odd Fests running worldwide as single-day events, the practical question is whether one is running near you. The Fests listing on the official site is the place to check. Fests are one day, in person, and generally free.

The global online track runs the whole month and includes livestreams, DEV mini-challenges and Global Hack Week. If you cannot get to a Fest, or your city has none, this is the lower-commitment route and the one most people should take.

Two honest warnings. Fests fill, and the popular ones are usually full well before October. And in-person events are a networking opportunity first and a coding opportunity second — the people you meet are worth more than the diffs you ship.

If you are a student

Hacktoberfest has no student requirement and no eligibility test, which makes it one of the lowest-barrier things on this list. It is also, for that reason, not a differentiator on its own — everyone can claim it.

What makes it differentiatory is the specific contribution and the repository. If you are aiming at a career in AI or developer tooling, October is a reasonable month to make a visible contribution to a project you want to be associated with, because the goal is no longer a badge but a track record a maintainer can vouch for.

For students looking for events with actual prizes and deadlines rather than contribution credit, the round-up of student tech events open right now collects the ones with confirmed future deadlines.

Go here first

hacktoberfest.com — registration, dashboard and rules
hacktoberfest.com/fests — the in-person event list

DevStackIO publishes verified student event deadlines throughout the year, with the official link and the confirmed closing date for each. If you would rather not track thirty calendars yourself, the October round-up is the fastest way in, and new events get added as organisers confirm dates.