In looking at the Travis-CI build history, the last build on master says about a year ago, so it does seem as though the unknown coverage on Coveralls may be due to the fact that we're diligent about not pushing directly to master (we submit PRs and merge those instead).
I'm going to push a single change (the same one in this PR) directly to master, which should trigger a build on that branch and we'll see if Coveralls starts displaying a valid coverage value.
I had noticed the change in
.env.example
, too, but came to the same conclusion, which is that the values have not changed in Homestead to match.Before we merge this, I want to try something else to fix the Coveralls issue as described in https://github.com/lemurheavy/coveralls-public/issues/1201 .
In looking at the Travis-CI build history, the last build on
master
saysabout a year ago
, so it does seem as though the unknown coverage on Coveralls may be due to the fact that we're diligent about not pushing directly to master (we submit PRs and merge those instead).I'm going to push a single change (the same one in this PR) directly to
master
, which should trigger a build on that branch and we'll see if Coveralls starts displaying a valid coverage value.