3 ms·
> Quite the opposite, the fixes should begin with a proper description of a problem. So the issue should get reported first. Especially for something as trivia
by faho 5y ago
> Quite the opposite, the fixes should begin with a proper description of a problem. So the issue should get reported first.
Especially for something as trivial as this, I don't see what value a separate issue adds.
If you want to have something to link to e.g. for your release notes, a PR can also do that job.
As an opensource maintainer, if someone opens an issue "Typo in docs" and a PR "Fix typo in docs #12345" five minutes later, I'll just tell them to not bother with the issue next time because that's just more clicking for me.
- PeterisP 5y agoThe key problem is that a PR can't do the job because of the CLA-related difficulties described in the original article - the submitter can make the issue for the trivial change but not make a PR so the expectation is that the actual trivial change would have to be done by someone who has already handled the CLA overhead.