<     May 2017     >
Su Mo Tu We Th Fr Sa  
    1  2  3  4  5  6  
 7  8  9 10 11 12 13  
14 15 16 17 18 19 20  
21 22 23 24 25 26 27  
28 29 30 31
00:20 ixti joined
01:50 nemothekid joined
02:00 rickmak joined
03:36 hcpl1 joined
04:28 hamishmack joined
05:11 yongu_ joined
05:12 yongu_ left
05:26 canvon joined
05:31 lpin joined
05:48 siovene joined
05:59 Sound joined
06:18 indistylo joined
06:27 mns joined
06:59 mtodor joined
07:12 raphink joined
07:12 raphink joined
07:27 moongazer joined
08:11 indistylo joined
08:27 trevor joined
08:42 raphink joined
08:42 raphink joined
08:50 gabizou joined
08:51 flix joined
08:51 flix joined
08:51 nicoulaj joined
08:56 aruns joined
09:09 raphink joined
09:09 raphink joined
09:39 riemann joined
09:53 hamishmack joined
09:57 jantman joined
10:18 ZyX-I joined
11:25 hcpl1 joined
11:59 davehunt joined
12:12 martinisoft joined
12:33 jeffreylevesque joined
13:11 Sound joined
13:39 moongazer joined
14:29 kso512 joined
14:44 rickmak joined
14:47 npmccallum joined
15:08 tkimball joined
15:08 rickmak_ joined
15:21 rickmak joined
15:38 rickmak_ joined
15:56 tkimball joined
16:13 mtodor joined
16:38 thunderbolt joined
16:38 <thunderbolt> Alright, so I have travis working on my open source project running tests. I'd like to setup travis to fail if linting ever GETS WORSE. Is this possible to do?
17:19 <jantman> IIRC that would have to be something outside of Travis itself. i.e. whatever defines "gets worse" would need to be in your code, or third party code
17:19 <jantman> personally, I usually use one of the free-for-open-source services that provide such functionality (codecov.io, landscape.io and a whole bunch of others similar)
17:38 riot joined
17:41 hcpl1 joined
19:25 hcpl1 joined
20:25 raphink joined
20:26 raphink joined
21:05 nemothekid joined
21:07 jeffreylevesque joined
22:18 nemothekid joined
22:26 Majost joined
22:29 antlarr joined
22:30 mvantellingen joined
22:33 ribasushi joined
22:37 Sound joined
22:42 dmj` joined
22:45 TheJJ joined