[bug] Coveralls API endpoint returns `null`

[miguelnietoa]

Hello, I am getting "INVALID RESPONSE DATA" for my coveralls badge (with shields.io).

Helpful links:

• Coveralls: https://coveralls.io/github/kommitters/kadena.ex
• Project: https://github.com/kommitters/kadena.ex
• How shields.io fetch data from Coveralls API: https://github.com/badges/shields/blob/master/services/coveralls/coveralls.service.js#L48-L63

---

1. Coveralls API endpoint returns null. Request: GET https://coveralls.io/github/kommitters/kadena.ex.json?branch=@ Response: null

2. If you enter this URL https://coveralls.io/github/kommitters/kadena.ex?branch=main Coveralls does not show the builds:

It seems like Coveralls does not recognize main as the default branch.

As additional info, I noticed this happens after this PR: https://github.com/kommitters/kadena.ex/pull/140 Notice that the base branch changed, maybe that's the reason?

---

Thanks for reading and hope this has a solution! 👍🏻

[afinetooth]

@miguelnietoa sorry for the delay here.

As of today I was not able to reproduce any of these issues, which is hopefully a good thing and, again I hope, suggests the issue may have been temporary?

For good measure, when this happens, it's always a good idea to re-sync your repo with Github, via settings (especially if you're aware of anything that may have changed on the Github side):

I did this (after not being able to reproduce any of the issues above, still), but we did register some change, however minor. But, after trying again, after that sync, still can't reproduce.

Did this go away on its own, or did you have to take further measures to fix it?

[miguelnietoa]

Hey @afinetooth 👋🏻

Well, now it is fixed. I just re-sync via settings and in the next PR merged into main seems like the issue was fixed...

So yeah, it was temporary and now there is no problem! Hopefully, as you mention 😅

[miguelnietoa]

Closing this issue. Thanks @afinetooth