Menu

6 Merged Patches Later: How to Get Your First PR Accepted in a Big Open-Source Repo
📰

6 Merged Patches Later: How to Get Your First PR Accepted in a Big Open-Source Repo

DEV Community: beginners·Sh Raj·2 days ago
#aArPrRpu
#devtobeginners#devto#dev#first#merged
Reading 0:00
15s threshold

I am a computer science student with no industry connections. So far I have had six patches merged upstream: a cancellation fix in Google's gemini-cli, three fixes in MoFA's Rust crates, a types fix in Preact, and an inline-toolbar fix in Editor.js — with fourteen more in review. None of that happened by luck. The process is learnable, and it is mostly about making the reviewer's job easy.

1. Reproduce first, always

Every one of my merged PRs started from a failing case I could reproduce. Not a vague idea — a concrete sequence that shows the bug happening. If you cannot reproduce it, you do not understand it yet, and your fix will be a guess. Write the reproduction down; it becomes the first paragraph of your PR description, and it is the thing that makes a maintainer take the report seriously.

My gemini-cli fix started exactly this way: cancel a turn mid-compression, observe the request continuing. The MoFA fix started with a bad cron schedule string panicking on unwrap() .…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.