Skip to content
This repository has been archived by the owner. It is now read-only.

Only run report in coverage script - Closes #379 #385

Merged
merged 1 commit into from Dec 5, 2017

Conversation

2 participants
@willclarktech
Copy link
Contributor

commented Dec 5, 2017

As opposed to running the full suite of tests again

Closes #379

:bowtie: Only run report in coverage script
As opposed to running the full suite of tests again

Closes #379

@willclarktech willclarktech self-assigned this Dec 5, 2017

@willclarktech willclarktech requested a review from Tosch110 Dec 5, 2017

@willclarktech willclarktech added this to Pull Requests in Version 1.0.0 Dec 5, 2017

@willclarktech willclarktech added this to Pull Requests in Sprint Board 04-12-17 Dec 5, 2017

@willclarktech willclarktech merged commit 4868971 into 0.4.0 Dec 5, 2017

3 checks passed

continuous-integration/jenkins/lisky The build passed.
Details
continuous-integration/jenkins/pr-merge This commit looks good
Details
coverage/coveralls First build on PR-385 at 100.0%
Details

@willclarktech willclarktech deleted the 379-coverage_report_script branch Dec 5, 2017

@willclarktech willclarktech moved this from Pull Requests to Merged Pull Requests in Version 1.0.0 Dec 5, 2017

@willclarktech willclarktech moved this from Pull Requests to Merged Pull Requests in Sprint Board 04-12-17 Dec 5, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.