On testing culture in GitHub projects

Maybe for documentation or source-comment fixes, but most code fixes should have one or more unit tests to accompany them. To me, a pull request represents something that should be pretty close to finished work. There may be a few style issues to clean up but it should be functionally done.

If someone wants to discuss how to approach or solve a problem in general without working and tested code, I'd prefer to see that happen in the bug/issue rather than a pull request. Otherwise it can lead to wasted effort and/or hurt feelings on the part of the contributor.

Either I fixed the problem or traffic has simply gone down enough.

Totally embarrassing. I'm trying to get it running again.

That is the site, demonstrating what a lack of testing gets you. It's brilliant.