How to Contribute to Open Source (And Actually Get Merged)

"Contribute to Open Source" is generic advice. Here is the specific playbook to making your first meaningful contribution.

1. Finding the Project

Don't start with React or Linux. They are too complex. Look for:

Tools you use daily (e.g., a VS Code extension, a small npm package).
Projects with < 1k stars but active.
Labels: good first issue, help wanted.

2. The Setup

Fork -> Clone -> Branch. Run the tests immediately. If tests fail before you touch code, you need to fix your environment first.

3. Finding an Issue

Don't just look at the issue tracker. Look for Reproducing Bugs.

Go to issues labeled bug.
Try to reproduce it locally.
If you can reproduce it, comment: "I can reproduce this on Node 18. I'm investigating."

This creates value even if you don't fix it!

4. The Communication

Before writing 100 lines of code, open an issue or comment. "I plan to fix this by adding a check in utils.js. Does that sound right?"

Maintainers love this. It saves them from reviewing code they didn't want.

5. The Pull Request (PR)

Title: Clear and present tense. "Fixes crash on login" (Not "Fixed").
Description:
- What was broken?
- How did you fix it?
- How to test it?
Tests: ALWAYS include a test case that fails without your fix and passes with it.

6. Handling Feedback

You will get comments. "Change variable name", "Move this file". Do not argue. Say "Good point, updating." and do it. Maintainers are usually tired volunteers. Make their life easy.

Why Do It?

Resume: "Contributor to Material UI" > "Built To-Do App"
Learning: Reading good code makes you a better coder.
Networking: I've gotten job offers directly from maintainers.

Start small. But start real.