Home / Programs / 24 Pull Requests

24pullrequests

Organized by 24pullrequests

24 Pull Requests

One pull request a day through December, given back to the projects you use.

FreeNo applicationOne monthAny repositoryMaintainer-first

About the program

24 Pull Requests asks for one thing through December: give back one pull request a day to the open-source projects you already use. There is no application round, no mentor matching and no shortlist - the calendar is the whole programme, and it reopens every year on 1 December.

Maintainers take part the other way round. They post to the project expo listing the work they would actually like to see done, so the December traffic lands on tasks someone volunteered to review instead of arriving cold. That single habit is why the drive works at all: the pull requests go to repositories whose owners asked for them.

Nothing is paid. The reward the organizers describe is the gift itself, which makes it the cheapest serious contribution streak available - and the one most likely to be read by a maintainer in January, when the tree is quiet.

Primary stack

Any GitHub language

Technical focus

DocumentationIssue triageBug fixesTest coverage

The path

  1. 01
    December 1 - pick a project

    Open the expo on 24pullrequests.com and choose from what maintainers listed, or work on the repository you already depend on.

  2. 02
    One pull request a day

    There is no size rule. A docs fix, a repro report or a small test counts the same as a feature on any of the 24 days.

  3. 03
    Keep the streak visible

    Your December activity is public record on GitHub; the site tracks your contributions against the calendar.

  4. 04
    December 24 - hand it over

    Merge or leave the work open for review. Nothing is graded, and no certificate gates the next cycle.

Who it's for

  • First-time contributors who want a low-stakes reason to open their first pull request
  • Developers rebuilding a contribution history after a quiet year
  • Maintainers who want December backlog work to arrive through an explicit ask rather than cold outreach

What you walk away with

  • A public month of merged and opened pull requests across real projects
  • Direct contact with maintainers whose software you already run
  • A habit-forming month that reads well in a later GSoC, LFX or Outreachy proposal
  • No cost, no application deadline and no risk of being rejected

Program timeline

Calendar positions for the 2026 cycle - the marker shows October, where you are now.

Nominations & prep
Contribution drive
JanFebMarAprMayJunJulAugSepOctNovDec
  • Nominations & prepNov - Dec
  • Contribution driveDec - Jan

Organizations

Reading the participation record...

// keep going

More programs we track

Everything else on the calendar - 12 other mentored routes from first PR to paid season.