we have build bots that produce coverage reports, e.g. https://storage.googleapis.com/chromium-v8/linux64_gcov_rel/35b6aa38497fdd1ea08af7d4042528c645826b06/index.html We currently don’t have alerts set up for this. We also do not enforce a specific % of code coverage (which is fine!).

However, it would be nice if % coverage change per file would be displayed on https://chromium-review.googlesource.com/ for each CL once the bots complete their runs. This way, engineers can get an idea of the impact of their CL on code coverage before it lands, without having to manually navigate to the coverage report every single time.

Here’s a similar example of this kind of thing on GitHub: https://github.com/mathiasbynens/he/pull/55#issuecomment-302787905