Commit c9e6dc0
fix: fallback to create when GitHub check run update returns 404 (#710)
* Initial plan
* Initial exploration: Understand the issue with GitHub Checks API 404 handling
Co-authored-by: crenshaw-dev <[email protected]>
* feat: add 404 fallback for GitHub Checks API update operations
When a CommitStatus was created using the legacy Commit Status API instead
of the Checks API, it may have an invalid check run ID. When attempting to
update such a check run, GitHub returns a 404 error. This change detects
404 errors and falls back to creating a new check run instead, allowing
the transition from Commit Status API to Checks API to work seamlessly.
Co-authored-by: crenshaw-dev <[email protected]>
* chore: revert unrelated package-lock.json changes
Restored package-lock.json files to their original state before the PR.
These changes were not related to the GitHub Checks API fix.
Co-authored-by: crenshaw-dev <[email protected]>
---------
Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: crenshaw-dev <[email protected]>1 parent 82fa8f5 commit c9e6dc0
1 file changed
+12
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2 | 2 | | |
3 | 3 | | |
4 | 4 | | |
| 5 | + | |
5 | 6 | | |
| 7 | + | |
6 | 8 | | |
7 | 9 | | |
8 | 10 | | |
| |||
158 | 160 | | |
159 | 161 | | |
160 | 162 | | |
| 163 | + | |
| 164 | + | |
| 165 | + | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
| 170 | + | |
| 171 | + | |
| 172 | + | |
161 | 173 | | |
162 | 174 | | |
163 | 175 | | |
| |||
0 commit comments