Contributions count too.
A merged pull request is real, verifiable proof you can ship — reviewed by a maintainer, out in the world, and yours to point to on a resume. No visa, no sponsor, no employer required, just a repo and a first PR. Join a structured program or a repo below — each comes with what it takes to get a PR merged there.
Put it on your resumeOpen programs & repos
Before your first PR
- 1
The rules have tightened
AI-generated PRs flooded big repos, so many now auto-close outside PRs that don't link an approved — sometimes assigned — issue. Read CONTRIBUTING.md every time; last year's advice may be wrong.
- 2
Own every line, write every reply
Use AI to code if you like, but disclose it and be able to explain each change. Several repos close or ban for AI-written PR descriptions and review replies.
- 3
One open PR per repo
Until your first one merges. Reply to reviews within a day; if nothing happens for a week, one polite ping.
- 4
Reproduce on latest main first
Then check nobody's already on it — search open PRs for the issue number. Duplicates are closed without a word.
- 5
A failing test is your proof
A regression test that fails before your fix and passes after is the fastest way to a yes — llama.cpp may close a fix without one.
- 6
Green CI before you ask
Run the repo's own lint, type and test commands locally. Handle sign-off too: DCO repos need git commit -s, CLA repos need a one-time signature.
Finding more
- Good First Issue ↗
Curated beginner issues across popular repos
- Up For Grabs ↗
Projects that tag tasks for newcomers
- CodeTriage ↗
Emails you a few issues a day from repos you pick
- DeepWiki ↗
Ask questions about any public repo's codebase
- GitHub label search ↗
Unassigned good-first-issues anywhere on GitHub