I would’ve rejected the PR too, but not for violation of that rule, but because one-line changes that merely fix a comment waste everyone’s time reviewing it, and are often just to build someone’s resume. I’ve even seen some that remove trailing whitespace.
If you want to fix it alongside other changes, go for it (and the reviewer said as much on the PR). But if you’re only interested in sending in drive-by commits to build a resume or something and aren’t actually interested in helping, then it should be rejected as noise.
If there’s a broader pattern of this, maybe that’s cause for concern. But if it’s literally just this instance, I could see the dev being annoyed at drive-by PRs.
I would’ve rejected the PR too, but not for violation of that rule, but because one-line changes that merely fix a comment waste everyone’s time reviewing it, and are often just to build someone’s resume.
That’s exactly what I was talking about. You’re taking what they said reasonably, because you’re probably a reasonable person! However, look at what they’re actually saying. The issue wasn’t framed as being a “drive-by,” though later that’s what they claimed. It was about ideology. It was about politics. They didn’t pull up rules about one-line changes to justify not accepting them, they pulled up rules about talking politics.
The problem wasn’t that it was a meaningless PR, the problem was that it was a meaningful PR that they disagreed with.
And, quite frankly, disagreeing with that does make you an asshole, at the very least, and a transphobic misogynist, at worst. There were at least a few PRs open about similar issues, too.
Look, I’m not calling him a transphobe or a misogynist; I’m just saying this was an asshole thing to do, and it was done in an asshole way, and that allowing this sort of thing to exist, especially in FOSS, is not good. That’s all.
I would’ve rejected the PR too, but not for violation of that rule, but because one-line changes that merely fix a comment waste everyone’s time reviewing it, and are often just to build someone’s resume. I’ve even seen some that remove trailing whitespace.
If you want to fix it alongside other changes, go for it (and the reviewer said as much on the PR). But if you’re only interested in sending in drive-by commits to build a resume or something and aren’t actually interested in helping, then it should be rejected as noise.
If there’s a broader pattern of this, maybe that’s cause for concern. But if it’s literally just this instance, I could see the dev being annoyed at drive-by PRs.
That’s exactly what I was talking about. You’re taking what they said reasonably, because you’re probably a reasonable person! However, look at what they’re actually saying. The issue wasn’t framed as being a “drive-by,” though later that’s what they claimed. It was about ideology. It was about politics. They didn’t pull up rules about one-line changes to justify not accepting them, they pulled up rules about talking politics.
The problem wasn’t that it was a meaningless PR, the problem was that it was a meaningful PR that they disagreed with.
And, quite frankly, disagreeing with that does make you an asshole, at the very least, and a transphobic misogynist, at worst. There were at least a few PRs open about similar issues, too.
Look, I’m not calling him a transphobe or a misogynist; I’m just saying this was an asshole thing to do, and it was done in an asshole way, and that allowing this sort of thing to exist, especially in FOSS, is not good. That’s all.
Check this out: https://mkultra.monster/tech/2024/07/03/serenityos-and-ladybird