3 ms·
Small PRs are great, IME. They're much easier to handle than bigger ones, so there are rarely downsides for maintainers. Coding standards and formatting are ra
by ratww 5y ago
Small PRs are great, IME. They're much easier to handle than bigger ones, so there are rarely downsides for maintainers.
Coding standards and formatting are rarely an issue in small PRs. Even if I don't have a CI, I can just run the linter/formatter on my side, or even fix by hand if it's small enough. Worst case? You get a code review.
Bug fixes are certainly always welcome, even if you just paste the fix in a Github Issue. Even just a reproduction is good enough and very welcome. Non-code contributions are also contributions.
Typos and change of phrasing? Adding examples to the documentation? Quick to check and quick to merge, awesome.
I'd say the only "small" contributions I ever denied were things that didn't add at all to the project: someone who tried to add hand-drawn logos to several of my repositories, trying to change the license, code that caused bugs or security issues and we couldn't really fix it, one-line PRs to the readme join the contributor's list, etc.