I added in the .codeclimate.yml file during my changes in #24, but in order to get CodeClimate to run against your repository you'll need to login to https://codeclimate.com/ with your GitHub account and add the repo. It's free for open-source (public repo) projects and adds a CI tool which runs automatically on each commit to master branch to trigger a run of Rubocop, RSpec, and SimpleCov with reporting.
The SimpleCov configuration I provided in my changeset is set to expect 51% coverage with unit tests, however there are currently no unit tests in the repo. I see #7 is open about this. If you'd like, I'm happy to start writing some unit tests as a follow-up later this evening my time. Just wanted to make sure I gave you the rundown on this stuff and I didn't really document it well in my PR.
This is just an informational issue since I didn't have a better way to contact you directly, but you can use it to track your work against adding CodeClimate if you'd like.
Howdy Lyle,
I added in the
.codeclimate.ymlfile during my changes in #24, but in order to get CodeClimate to run against your repository you'll need to login to https://codeclimate.com/ with your GitHub account and add the repo. It's free for open-source (public repo) projects and adds a CI tool which runs automatically on each commit tomasterbranch to trigger a run of Rubocop, RSpec, and SimpleCov with reporting.The SimpleCov configuration I provided in my changeset is set to expect 51% coverage with unit tests, however there are currently no unit tests in the repo. I see #7 is open about this. If you'd like, I'm happy to start writing some unit tests as a follow-up later this evening my time. Just wanted to make sure I gave you the rundown on this stuff and I didn't really document it well in my PR.
This is just an informational issue since I didn't have a better way to contact you directly, but you can use it to track your work against adding CodeClimate if you'd like.
Cheers and thanks again for the useful tool.