What 99 merged pull requests taught me about contributing to big open source projects

说明与用途

作者分享了如何通过测试验证、最小化改动和清晰说明根本原因，成功将99个小 bug 修复 PR 合并到大型项目中。

问题

Contributing small bug fixes to large open‑source projects can be challenging due to review load, conventions, and the need for clear root‑cause explanations.

结果

The author achieved 99 merged PRs, learned that small, root‑cause focused fixes are preferred, and gained insights into maintainer expectations and review practices.

工作流

• 1. Identify a bug that can be proven with a failing test.
• 2. Search open/closed PRs and issues to avoid duplication.
• 3. Write a minimal change that fixes the root cause.
• 4. Add a test that fails before the change and passes after.
• 5. Follow repository conventions (commit style, PR template, CLA/DCO).
• 6. Run linters/formatters and ensure signed commits if required.
• 7. Submit PR with a concise description explaining the root cause.
• 8. Respond promptly to review comments.

证据

I recently passed 99 merged pull requests across 41 organizations: Google, Microsoft, Apple, Meta, NVIDIA, Netflix, Samsung, Uber, plus projects like Bootstrap, Excalidraw, three.js, MUI, Tailwind CSS and Puppeteer.

来源

The best contributions I made all had one thing in common: before touching the code, I could write a test that failed.

来源

I also follow each repository's own conventions: commit message style, PR template, changelog or changeset files, CLA or DCO.

来源