You are only a Kontributor when Its a KDE repository.
Typing characters is maybe 1% of the job. The other 99% is understanding how the change affects everything else. Changing a single line of code in a function called by 1000 other functions each themselves called in 10 other functions can still potentially be more work and a bigger change than changing 9000 lines of code in a function called once.
I once fixed a bug in credit card payment form because someone had gotten some formatting character screwed up and used a capital M in some place where a lower case m should have been. Since it was a payment system they couldn’t take payment for a while whilst that was screwed up. I was contracting there and happened to notice it. Sometimes all it takes is one character.
And your typo fix kickstarts 10 workflows, downloading gigabytes of data and running endless tests.
Depending on the size of the project, this may be an environmental concern.
When your PR to replace one line of code actively contributes to climate change.
I knew a guy who boasted about the number of repositories he created on Github. Said he created over four thousand.
I took a look. He did in fact sit down and create over 4,000 different, unique repositories. Each with a README and some slight variation on a few lines of code. That’s some kind of dedication, I guess?
Was he a Go developer before generics? Published 4000 versions of the library, one for each type.
No, it was mostly short bash/python/php scripts.
Maybe he automated it?
And maybe he published it on GitHub?
That’d be funny. Seeing
mass-repo-creatorand then 4000 random repositories below it.
When they reject your PR because you still managed to slip in a bug
If it involves pointers, not unlikely.
