Showing warning/error annotations the way Github does would be a huge win. We take warnings into account when reviewing a PR, even if the CI step itself passes. This is the biggest difference that keeps us mostly on Github’s UI. We review there and jump to Graphite to execute merges after approvals happen on Github. https://app.graphite.dev/changes-requested#request-o0i0TzYJajcPipNR9wDs Here’s an example of a CI check that highlights a potentially dangerous change of introducing a new enum value within a GraphQL schema. This warning doesn’t get surfaced at all in Graphite today.