#49630: ci: handle PRs with no checks in rerun apply patches
Merged
Description of Change
There's an edge case that I wasn't aware of before, where gh pr checks exits with a non-zero exit code if there are "no checks reported" for a PR. This seems to be the case for some old PRs that are in merge conflict state.
This PR refactors the workflow to use gh pr view instead, which has all the same information we need, in slightly different named fields. Since gh pr view is just for viewing a PR, it won't fail on this edge case, statusCheckRollup will just be an empty array.
Checklist
- PR description included
Release Notes
Notes: none
Backports
Semver Impact
Major
Breaking changes
Minor
New features
Patch
Bug fixes
None
Docs, tests, etc.
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron