html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue https://github.com/pydata/xarray/pull/1919#issuecomment-369117775,https://api.github.com/repos/pydata/xarray/issues/1919,369117775,MDEyOklzc3VlQ29tbWVudDM2OTExNzc3NQ==,12229877,2018-02-28T04:27:16Z,2018-02-28T04:27:16Z,CONTRIBUTOR,"Last time I used it Hound *didn't* update the PR status, so if so that removes one of my objections 😄 As a maintainer I prefer automating checks - I make mistakes, especially when tired, and it's nice knowing that the system has my back. Hound only runs checks in the diff range though, so I think it's still valuable to keep running flake8 ourselves. Trying both for a few months before making a final decision sounds like a good idea to me!","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,297794911 https://github.com/pydata/xarray/pull/1919#issuecomment-369111117,https://api.github.com/repos/pydata/xarray/issues/1919,369111117,MDEyOklzc3VlQ29tbWVudDM2OTExMTExNw==,12229877,2018-02-28T03:38:47Z,2018-02-28T03:39:07Z,CONTRIBUTOR,"[home-assistant](https://github.com/home-assistant/home-assistant) uses https://houndci.com, and it seems to work pretty well for them - it just leaves a review with any flake8 comments at the relevant lines of the pull. Note that while HoundCI is used to provide faster and more readable feedback to contributors, they still check flake8 in Travis to ensure everything is fixed before merging.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,297794911 https://github.com/pydata/xarray/pull/1919#issuecomment-369106191,https://api.github.com/repos/pydata/xarray/issues/1919,369106191,MDEyOklzc3VlQ29tbWVudDM2OTEwNjE5MQ==,12229877,2018-02-28T03:05:48Z,2018-02-28T03:05:48Z,CONTRIBUTOR,"I would be very disappointed to remove the flake8 check from Travis - in my experience, style guides are only applied *consistently* if they are enforced by CI. Ensuring that each pull maintains our standards is much less burdensome than regular ""big push"" efforts to get back to the standard (see eg #1741 and #1824 - it took two people!), **and** avoids periods of lower code quality. In short, I think that Travis *is* the right place to put these checks - review bots are a complement, not a substitute.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,297794911