Yeah, that is the case. I massaged the GitHub API logs[0] with jq to make a readable version of the issue history[1]. I was firstly (based on the blog post) fe

Yeah, that is the case. I massaged the GitHub API logs[0] with jq to make a readable version of the issue history[1]. I was firstly (based on the blog post) feeling bad about the maintainer... but after reading the issue report, it turns out multiple people were working on the issue and the author responded... 'this patch is boring'. That's... certainly not good to people who are trying to resolve the issue. He even goes to threatening to delete the organization if people talk about the issue. [0] https://gist.github.com/bb010g/705c8ffe4b9db9550a7782d25e5a53be https://gist.github.com/bb010g/705c8ffe4b9db9550a7782d25e5a5... [1] https://gist.github.com/pcr910303/d7722a26499d0e9d2f9034a06f2433b4 https://gist.github.com/pcr910303/d7722a26499d0e9d2f9034a06f...