I posted this as a question to StackOverflow, but thought it might be more effective to post it here as an issue. The text from that post is as follows:

I have a GitHub repository established with a Multibranch Pipeline job in Jenkins, and until now have been content to require the continuous-integration/jenkins/branch status check, as Jenkins posts when building a local branch from the repo. However, I've now got a pull request from an external fork, and Jenkins has posted a continuous-integration/jenkins/pr-merge status check for that. And because the continuous-integration/jenkins/branch status check is required, the PR is blocked from being merged.

What's the expected approach here, for a project that will have a combination of local branches (from its primary maintainers) and forks (from occasional outside contributors)? Must I forgo having either of the status checks be required on the GitHub side? Or is there some other way to get Jenkins to post a stable status check context regardless of the PR's source?

So, given that forks will cause a continuous-integration/jenkins/pr-merge status to be posted to the repo, but local branches will cause a continuous-integration/jenkins/branch status to be posted, is there any expected way to make a Jenkins-originated status check required on the GitHub side?