CLA checks are stuck in Pending

[vcsjones]

The CLA checks appear to be stuck in Pending, blocking PRs from merging.

Example PRs: #65404, #65432, #65435.

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The CLA checks appear to be stuck in Pending, blocking PRs from merging.

Example PRs: #65404, #65432, #65435.

Author:	vcsjones
Assignees:	-
Labels:	area-Meta
Milestone:	-

[danmoseley]

internal reference --

AZUREDEVOPS · BUG
1919062

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The CLA checks appear to be stuck in Pending, blocking PRs from merging.

Example PRs: #65404, #65432, #65435.

Author:	vcsjones
Assignees:	-
Labels:	area-Infrastructure
Milestone:	-

[jeffhandley]

Once the service is back up and running, PRs can be "poked" to have the check re-run. The instructions are captured here:
https://github.com/dotnet/runtime/blob/main/docs/pr-builds.md#additional-information

In the rare case the license/cla check fails to register a response, it can be rerun by issuing a GET request to https://cla.dotnetfoundation.org/check/dotnet/runtime?pullRequest={pr_number}. A successful response may be a redirect to https://github.com.

[danmoseley]

It's OK to merge PR's meantime that are from folks who we know have write access to the repo. They clearly already signed the CLA. I confirmed this offline. You would have to ask your neighborhood admin.

[jeffhandley]

The service is back up and running. I re-ran validation for the 3 PRs mentioned above to verify.