Hi folks,
So, I was reviewing one of @meeber's recent PR and I noticed our coveralls reports (and therefore our coverage badge) is not working.
As you can see in this link the most recent build happened in 2015.
I'll take a look at it this weekend but if any of you have any ideas on why this is happening please let me know.
Thanks 馃槃
Looks like it was purposefully removed back in early 2014 due to reliability concerns per #236.
The lone 2015 build coverage must've been submitted manually.
So, do you think we should re-enable it? IMO we should either enable it or remove the coverage badge. It makes no sense to have coverage information that is not accurate.
I don't have a strong opinion. I guess my preference would be to remove the badge for now and then add the badge and functionality back in after we refactor Chai to not use makefiles.
Hello guys :smile: , i have some news.
Perhaps the cause is
lemurheavy/coveralls-public/issues/603,
since last build recognized is before the repository transferred (just assumption). Maybe we can change to https://codecov.io,
I was looking at codecov, investigating if we can move to that. It is more actively worked on and it is part of the GitHub marketplace.
No more response, i guest the other are agree? Shall i work on it?
preview:

I notice when we integrate codecov app we will get comment on PR, i hope it will give an ease to our outstanding maintainer :smile: . CMIIW
Most helpful comment
I don't have a strong opinion. I guess my preference would be to remove the badge for now and then add the badge and functionality back in after we refactor Chai to not use makefiles.