perf: budget review prompt file patches#68
Open
stainlu wants to merge 1 commit into
Open
Conversation
0b1168d to
20f5662
Compare
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.
Summary
dashboard/in CI sparse checkout so the existing dashboard worker test can run on PRs.Why
Large OpenClaw PRs can hydrate up to 80 PR files, and each file previously kept up to 2k chars of patch text. That can push roughly 160k chars of repeated diff hunks into every review prompt. This keeps the metadata breadth while bounding diff-token pressure.
The CI sparse checkout already included
test/, but omitted trackeddashboard/, sotest/dashboard-worker.test.tsfailed to importdashboard/worker.json GitHub. This branch includes the minimal workflow fix needed for CI parity.Validation
pnpm run buildpnpm run format:checkpnpm run test:unitgit diff --checkNote
pnpm run checkfails locally on two existing notifier repair tests under Node 22. The repo requires Node 24+, and I reproduced the same local Node 22 failures on cleanupstream/main; this branch build, format, and unit surface are green.