Remix.run Logo
▲ stevelacey an hour ago

I sent a handful of PRs to rebing/graphql-laravel a few years back, and the ones that got merged were all small and self-contained. A maintainer's scarce resource is review time, not ideas, so anything that makes a diff cheap to judge (one concern per PR, a test, a short explanation of why) counts for more than how clever the change is.

The flood you're describing is the same problem with the cost of writing a patch pushed to zero while the cost of reviewing one stays the same.