Joe Downs

Before it's merged, should this be `pull_request_target` for the run event? Or is it okay for the commit checker to not run on PRs with merge conflicts?

Okay, the event trigger has been changed to `pull_request_target`. As far as the functionality of this action, it should be ready to merge.

Hmm. That's strange. [This stackoverflow discussion](https://stackoverflow.com/questions/52200096/github-pull-request-waiting-for-status-to-be-reported) seems to suggest it's just a *thing* that happens with Actions sometimes, and re-triggering them should fix it. [This GH community discussion](https://github.com/orgs/community/discussions/26698) mentions renaming...

I don't *think* it's related to any branch protection rules. I had the same `Expected — Waiting for status to be reported` message on [the PR in my fork](https://github.com/Joe-Downs/ompi/pulls?q=is%3Apr+is%3Aclosed) and...

@jsquyres Welp, looks like we have a problem with the Commit Checker. In PR #10663, the bot ran, but had an error. [Notably this:](https://github.com/open-mpi/ompi/runs/7826430088?check_suite_focus=true) ``` stderr: 'fatal: ambiguous argument 'main..origin/typos/remaining':...