The Contribution · Free & open · 5 chapters published

How to Contribute to Open Source

by M. Ali Adnan

A practical guide to finding projects, making your first contribution, and growing into a trusted open-source maintainer.

From your first Issue to your first Merge — step by step.

Start reading Browse chapters

38 merged pull requests — Google · OpenAI · n8n · OpenClaw

How to Contribute to Open Source — book cover

Our mission

“Make your first merged pull request inevitable — and show every reader that open source is a process they can learn, not a club they have to be invited into.”

01 — The book

What's inside this book?

Open source feels intimidating until your first merged pull request. This book removes the guesswork — written from real experience, not theory.

Find the right project

Discover projects that match your skill level and interests.

Ship your first PR

A step-by-step walkthrough of fork → branch → pull request → merge.

Master the unwritten rules

Communication, code review etiquette, and issue etiquette maintainers notice.

Grow into a maintainer

Go from first-time contributor to someone trusted with a project's future.

The loop this book teaches

One repeatable cycle — mastered in Chapters 1–3

Who this book is for

Reader	What you'll get
Students & self-taught devs	A repeatable path from zero to a merged PR — no CS degree assumed.
Career-switchers	Public proof of skill: merged contributions recruiters can click.
Working developers	The unwritten rules of review etiquette and maintaining trust.
The AI-curious	Chapter 4: a supervised AI workflow that runs your PR loop with you.

02 — Find your path

Start where you stand

Everyone climbs the same ladder — and you can stop at any rung. Pick the route that matches your experience today.

Just curious

Understand what open source is and why it pays — then decide.

Chapter 1 · ~20 min

Ready to contribute

Recommended

Understand, set up your toolkit, and ship your first merged PR.

Chapters 1 → 3 · ~1 hr

Already contributing

Automate the loop with an AI pair contributor, then build reputation.

Chapters 4 → 5 · ~45 min

03 — About the author

M. Ali Adnan

@AAliKKhan

Full-Stack Developer & Agentic AI Builder · Karachi, Pakistan

I started coding publicly on April 2, 2024 with zero open-source experience — just assignments pushed to GitHub. Since then I've shipped 73 public repositories and had 38 pull requests merged into projects people actually use — including google/adk-docs, openai/openai-agents-python, n8n-io/n8n-docs, and openclaw/openclaw. I learned every rule of collaboration the hard way: broken builds, silent reviewers, rejected PRs, and finally merged ones. This book is the guide I needed on day one.

GitHub LinkedIn alicodez.com

Pull requests merged into

Google ADK Docsgoogle/adk-docs · ×21 merged

OpenAI Agents SDKopenai/openai-agents-python · ×7 merged

OpenClawopenclaw/openclaw · ×3 merged

n8n Docsn8n-io/n8n-docs · ×1 merged

Google ADK Docsgoogle/adk-docs · ×21 merged

OpenAI Agents SDKopenai/openai-agents-python · ×7 merged

OpenClawopenclaw/openclaw · ×3 merged

n8n Docsn8n-io/n8n-docs · ×1 merged

04 — The journey

My open source journey

I'm M. Ali Adnan (@AAliKKhan) — Full-Stack Developer & Agentic AI Builder from Karachi, Pakistan. Here's the path that made this book possible.

Apr 2024

Started in public

First GitHub account. Assignments and experiments pushed openly from day one.

2024–25

Built in the open

73 public repositories — assignments, projects, and experiments.

Now

Merged into big projects

38 merged pull requests across 4 major platforms — Google, OpenAI, n8n & OpenClaw.

Teaching what I learned

This book — everything I wish someone had told me before my first PR.

05 — Proof, not promises

Why trust this book?

Everything here comes from real, public work on GitHub — verify it yourself.

@AAliKKhanView GitHub profile →

Public repositories

Merged pull requests

Platforms merged into

2+ yrs

Building in public

Chapters published

Every claim is a link, not a bullet — see all 38 merged pull requests on GitHub.

06 — Table of contents

Chapters

Five chapters — read them in order, or jump to the part you need.

Start reading

Introduction to Open Source

What open source platforms actually are, what you gain by contributing, and the GitHub / pull request basics that power every collaboration.

✓ Explain what open source platforms are and where they live
✓ Name at least five concrete benefits of contributing
✓ Describe the fork → PR → merge cycle in your own words

1.1 What Are Open Source Platforms? · 1.2 Benefits of Contributing — What You Get · 1.3 GitHub, Pull Requests & How Code Gets Merged

~5 min

Start Contributing: From Zero to a Working Setup

Get hands-on: fork and clone a real project, configure Git and your dev environment the right way, and find issues that are actually meant for beginners.

✓ Fork, clone, and wire up origin/upstream remotes correctly
✓ Configure Git identity, authentication, and a project dev environment
✓ Find and claim a live good-first-issue the professional way

2.1 Fork and Clone — Getting the Code on Your Machine · 2.2 Setting Up Your Git Environment & Dev Setup · 2.3 How to Find Issues Meant for You

~6 min

Your First Pull Request

The full walkthrough: read the issue properly, make the smallest change that solves it, write a PR reviewers enjoy, handle feedback like a professional, and finish strong after the merge.

✓ Interrogate an issue and reproduce a bug before coding
✓ Ship a small, tested, well-described pull request
✓ Respond to code review calmly and get it merged

3.1 Read Before You Code: Understanding the Issue · 3.2 Make the Change: Small, Focused, Tested · 3.3 Write the Pull Request · 3.4 Handle Code Review Without Losing Your Nerve · 3.5 After the Merge: Finish the Loop

~7 min

Contribute with OpenCode: Your AI Pair Contributor

Install OpenCode, teach it your forked-and-cloned workflow with a system prompt, grant it GitHub access so it can open PRs — then command it to read maintainer review comments and fix them until your PR gets merged.

✓ Install OpenCode and connect it to a model provider
✓ Grant safe, permission-limited GitHub access (gh CLI / MCP)
✓ Write an AGENTS.md system prompt that runs your contribution workflow
✓ Command the review loop: fetch comments → fix → push → merge

4.1 Why Let an AI Do the Busywork? · 4.2 Installing OpenCode · 4.3 Giving OpenCode Access to Your GitHub · 4.4 The System Prompt: Forked, Cloned, Fix, PR · 4.5 Watching It Send Your First AI-Assisted PR · 4.6 The Review Loop: Fix What the Maintainers Ask Until It Merges

~9 min

Beyond the First PR: Building a Reputation

Turn one merged PR into a lasting presence: contribute consistently, communicate so maintainers trust you, take on bigger work, and grow into your first maintainer responsibilities.

✓ Build a sustainable contribution rhythm and portfolio
✓ Communicate in a way that earns maintainer trust
✓ Escalate from fixes to features using discussion-first work
✓ Take on your first maintainer duties gracefully

5.1 Consistency Beats Heroics · 5.2 Communication That Makes Maintainers Trust You · 5.3 Leveling Up: Features, Discussions & Bigger Changes · 5.4 Your First Maintainer Duties

~6 min

Ready to make your first contribution?

Start reading today — it's free, and it starts with the basics.

Start reading Browse the glossary