Coveralls badges

[kubk]

The PR brings coveralls.io badges back. I've also removed Typescript/Prettier badges because nowadays these tools are de facto standard. Let's avoid excess information to not overwhelm reader.

Regarding allowing coveralls job to fail on CI, there is no clean solution yet, the issue is still open: actions/runner#2347

For example, one of the workarounds actions/runner#2347 would allow to merge a PR with optional failed job, but GitHub will show the whole PR as failed (with ❌ symbol).

@urugator How often do you encounter coveralls random fails?

Here coveralls job failed because the tests failed too: be29cd0

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0e61055

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[kubk]

https://github.com/mobxjs/mobx/tree/main/packages/mobx-react-lite#readme

Badges are too close to each other here (unlike in other READMEs in Mobx repo), I've added a bit of space

[urugator]

Do we know why it fails? To be clear I dunno if badges are always the cause. It seems quite random, so I thought it's because of race conditions or someting, but if it's just some service being unresponsive, then there is not much we can do I guess (besides increasing timeout).

[kubk]

@urugator Sorry for confusing you. The badges have nothing to do with CI. They just query some information from an endpoint and display it.

Regarding CI failures, I saw a few times how Coveralls Github action failed due to 504 from Coveralls API. Yes, there isn't much we can do because it seems like GitHub doesn't have a way to make job optional. In GitLab you can allow job to fail and still get the green pipeline: https://docs.gitlab.com/ee/ci/yaml/#allow_failure

Let's keep an eye on CI to understand how often we encounter such a situation. Then if it fails often, we can apply the workaround described in the PRs description. It should allow to merge even when optional job fails, but we'll still see the red X which might be a source of confusion.