In testing we saw that updating `ci-test-result` has a chance of failing if the correct check is not found. When we are creating the `ci-test-result` check via the Github Api, it successfully marked the PR check with the result. It did not seem to have any issue even if a `ci-test-result` job already existed By removing the logic of finding an existing check of the same name, and always creating the check, we assume this will improve the PR check updates fixes: #31601 |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| config-test.json | ||
| config.json | ||
| config.yml | ||
| labeler.yml | ||
| pull_request_template.md | ||
| release-drafter-template.yml | ||
| reviewers.yml | ||
| semantic.yml | ||