@slipset are you familiar with this issue? CircleCI confirmed this is because the PR submitter is logged out of, or never signed up with, CircleCI. In that case, the Circle workflows are just not run. Unfortunately, the error messages were addressed to me, and didn't mention the PR submitter, which led to a bunch of wasted time looking at other causes. From me: > Are you saying contributors submitting PRs who have never logged-in/signed up to CircleCI won't have our CI process run? That's a huge annoyance for an open-source project accepting PRs from the general public. > > Is there a way around this? Can we run all CI pipelines as a particular user or group? Not require PR contributors to login? Circle's response: > Our team has been making some changes to how we trigger pipelines depending on whether the committer is known to us or not, and this appears to be affecting Open Source projects like yours in a negative way. We are re-working this methodology and would like to implement something that won't cause the errors you see any longer. This process is already underway and we are working to get it released as soon as possible. > > Currently, our advice is that the user opening the PR should log in to CircleCI and then trigger the workflow again by re-pushing.