Re: [foreman-dev] HoundCI - annoying?

I feel actually quite the opposite, we used to have Hound via some external service and this feels much better integrated. Since github introduced reviews, Hound integration could take advantage of it in the future? They will implode once a review is confirmed, that could help. On the other hand,

Re: [foreman-dev] HoundCI - annoying?

On 01/11, Timo Goebel wrote: > Hi devs, > > I'm usually not very easily annoyed. What get's me started though > eventually is when things don't work properly. > HoundCI is one of those things. > > My main concern is, that I get an e-mail and/or Github notification for > every single comment. These

Re: [foreman-dev] HoundCI - annoying?

Hi, I agree that it is annoying to get a ton of messages from hound every time a new version of rubocop is released or when they change something in their default setup. Hound is working on using the review api but are currently running into some issues with it:

Re: [foreman-dev] HoundCI - annoying?

Hello, yes, I find it annoying and I liked the jenkins job more. It would be great if hound would be able to use reviews that would generate one email per review. Hopefully they work on it. Otherwise I'd be for moving back to jenkins. On středa 11. ledna 2017 12:07:38 CET David Davis wrote: >

Re: [foreman-dev] HoundCI - annoying?

Not sure if it helps you but you can filter out the HoundCI emails by checking for emails from "Hound ”. Also, when a HoundCI comment is addressed, isn’t the comment collapsed? I agree though that HoundCI doesn’t seem to work properly. On Katello, we’ve seen it add

[foreman-dev] HoundCI - annoying?

Hi devs, I'm usually not very easily annoyed. What get's me started though eventually is when things don't work properly. HoundCI is one of those things. My main concern is, that I get an e-mail and/or Github notification for every single comment. These can easily be ten or more e-mails.