Closed astrofrog closed 11 years ago
Woah I didn't know it would do that!
Ooo i have know idea what that comment means but, assuming it's a useful statement of coverage changing, that's pretty cool
I haven't played much with coveralls yet, but it seems nice. I'm fine if we turn it on, and add the extra fun travis/coveralls icons to the readme
So apparently @coveralls is a troll bot
I just added the status badges to the README.md in this pull request, and have also disabled the 'trolling' for now - I could see it getting annoying if it happens at every new set of commits in a PR!
Preview of the README.md file: https://github.com/astrofrog/dendro-core/blob/5f37fb1e4f5ec43f65a6b65b84965d3e431286e0/README.md
Cool. Anything that makes coding feel more like collecting pokemon is a win for me
Pokemon it will be then! :)
This is somewhat of a gimmick, but it's possible to get automated test coverage reports via http://coveralls.io - here is an example based on my branch:
https://coveralls.io/builds/140306
You can click on the filenames and see the coverage (and we can also exclude files if needed). Anyway, just wanted to suggest it, but I won't mind if other people think we should leave it out.