62a079ed12
Summary: The js_coverage step has failed on some recent PRs. While we want to continue collecting coverage data, we are not rejecting PRs that decrease coverage at the moment. Failing a PR in this step sends the wrong message, therefore, we should ignore whenever js_coverage fails. > The actual coverage failures appear to be issues related to coveralls (the coverage service) failing to map the coverage data to a specific repository, not necessarily due to a decrease in coverage. ## Changelog [Internal] Pull Request resolved: https://github.com/facebook/react-native/pull/27488 Test Plan: CircleCI. Differential Revision: D18962339 Pulled By: hramos fbshipit-source-id: 46cbe32c70ecc01324a703073f390dad0de562f4 |
||
---|---|---|
.. | ||
Dockerfiles | ||
DockerTests.md | ||
README.md | ||
config.yml |
README.md
Circle CI
This directory is home to the Circle CI configuration file. Circle is our continuous integration service provider. You can see the overall status of React Native's builds at https://circleci.com/gh/facebook/react-native
You may also see an individual PR's build status by scrolling down to the Checks section in the PR.