Repository navigation
ci: write Review only when it changes - #29
Merged
Merged
Conversation
Every Ready event reconciles every open PR, and each run wrote a pending Review before its checks and a success after them. A long-lived ready PR reached GitHub's limit of 1000 statuses per commit and context, after which every Ready run in the repository failed on that PR. A failed read still revokes a previous success. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
silveltman
marked this pull request as ready for review
October 30, 2026 14:37
An event about this PR, such as a Test rerun of its head, still writes pending before checking. A PR that changes while it is checked loses an old success. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the recurring Ready failures in fulldotdev/fulldev#606.
Cause. Every Ready event reconciles every open PR. For each ready PR the script wrote a pending Review before its checks and a success after them, so two statuses per PR per event, whichever PR or commit the event was about. In fulldev, Dependabot PR fulldotdev/fulldev#544 reached GitHub's limit of 1000 statuses per commit and context on 27 October at 18:10 UTC. Since then GitHub rejects every Review write on it (
This SHA and context has reached the maximum number of statuses.), and every Ready run in the repository fails on that PR, whatever branch triggered it. fulldotdev/fulldev#501 is at 362.Fix.
Checks
node --test tests/*.test.mjs: 53 passed. The two new tests fail onmain.After merge, callers need to pin the merged revision; fulldev gets that in its own PR.
🤖 Generated with Claude Code