When a CircleCI pipeline fails to start — due to a configuration error, a policy violation, or invalid YAML — there's currently no indication of this on your GitHub pull request. The workflow check never appears, leaving your team with no idea why CI didn't run without navigating to the CircleCI UI to investigate.

Beyond failures, there's also no good way for CircleCI to surface important but non-blocking messages on your PR — things like deprecation warnings, upcoming breaking changes, or policy warnings. These can't be communicated via a failed Checks status because that would block your PR from merging, so they often go unseen entirely.

We'd like CircleCI to post a comment directly on the PR in these situations, so developers can see what went wrong — or what they need to be aware of — without ever leaving GitHub. This would cover:

Pipeline not triggered due to invalid configuration or YAML errors

Pipeline blocked due to a policy violation

Pipeline triggered with a non-blocking warning (e.g. a deprecation notice or upcoming config change)

Important informational messages that don't warrant a build failure but are important to act on

This would keep developers in their natural workflow, reduce time spent hunting for errors, and make it easier to act on important warnings before they become bigger problems