10 PRs or One Giant: Choosing an Approach for Refactoring Jellyfin Helm Chart
People often ask me “how do I make my first PR?”, the answer is simple — just do it. But I want to write a series of notes about open source culture and how to make life convenient for everyone. Today we’ll look at a case I encountered yesterday, namely — multiple changes to one semi-abandoned repo. TL;DR When preparing a large refactor in an open source project: Break into small logical PRs — reduces cognitive load on reviewers Propose integration branch for coordination — allows incremental review and batch changes If in doubt, don’t hesitate to reach out to the team early — openness and communication matter Be ready for iterations — open source is about people This reduces load on reviewers and increases chances of successful merge. ...