Hacktoberfest 2026 swaps the PR quota for in-person Fests and an online swag track

Hacktoberfest drops the pull-request quota for 2026

Hacktoberfest has rebuilt its participation model for 2026. The familiar challenge — open four pull requests against any public repository during October and earn a shirt or a tree planting — is gone. In its place are one-day, in-person events called Fests, plus an online swag track whose requirements have not been published yet. The details come from a dev.to post published on 20 September, which draws on Hacktoberfest's own FAQ.

Why the rules changed

According to the FAQ as summarised on dev.to, AI tools made low-effort pull requests trivial to generate at scale, and volunteer maintainers were left wading through spam. Once a plausible-looking contribution became nearly costless to produce, the raw number of opened PRs stopped being a meaningful signal of real participation. Rather than bolting stricter spam filters onto the old format, the organisers rebuilt the event around physical attendance, which automated submissions cannot fake.

Fests replace the solo contribution sprint

The 2026 edition is run by Major League Hacking (MLH) and DEV, in partnership with DigitalOcean. Its centrepiece is a calendar of Fests: single-day, in-person gatherings that take one of two forms, a Hack Day or a Meetup, each running three to twelve hours and hosted by local organisers. The focus is hands-on building and learning — in particular with open-source AI and open-weight models — rather than individuals working alone to hit a quota. The dev.to author reads the format as aimed squarely at newcomers who never felt ready to submit a first contribution on their own, since a Fest provides talks, workshops and experienced people to ask in person.

What participants actually get

T-shirts survive, but only at in-person Fests, and even there they are not guaranteed: swag is shipped to organisers, who hand it out at their own discretion based on on-site supply. Online-only participants are explicitly not eligible for a shirt. Their track is a Swag Envelope of stickers and small items, earned by hitting online participation milestones that Hacktoberfest has not yet defined; the FAQ reportedly says only that more information is coming.

Finding or hosting an event

The dev.to post counted 217 Fests listed as of 20 September, using the event's public JSON API, and notes that the endpoint rejects bare requests sent without a User-Agent header. Coverage is uneven: the author found no Fest in Bulgaria, with the nearest listed events in the UK and Ankara, Turkey. Anyone can volunteer to host through the event's hosting page, though it is a genuine commitment — a venue, connectivity, seating and AV for a three-to-twelve-hour day. Because new events are added throughout October, the author suggests checking the live list before concluding nothing is happening nearby.

Ordinary contributions carry on

Nothing prevents anyone from contributing to open-source projects in October as in past years, the post notes; it is simply no longer a separately incentivised programme. Hacktoberfest's FAQ points newcomers to DEV's open-source getting-started guide for opening a first pull request.

Why it matters

The overhaul is a candid admission that AI-generated submissions broke the incentive design of a long-running community event, and it offers a template for how open-source programmes might respond: reward verifiable human presence rather than output volume. For contributors, the change trades remote, asynchronous participation — and its free shirt — for a lower-pressure, in-person on-ramp aimed at first-timers. For maintainers, October should get noticeably quieter. The trade-off is geographic: access now depends on having a Fest nearby or someone willing to organise one, and until the online milestones are published, remote participants have little concrete to aim for.