Repository navigation
Keep a warm scratch and add --interval - #24
Merged
Merged
Conversation
Reuse the scratch clone across grind runs, skip install when the lockfile is unchanged, and loop in-process with --interval so grind can stay running during a sprint. Co-authored-by: telivity-otaip <telivity-otaip@users.noreply.github.com>
telivity-otaip
marked this pull request as ready for review
October 21, 2026 02:22
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
Grind keeps its scratch clone under the system temp directory across runs instead of deleting it on exit. Reuse refreshes that clone from the open checkout’s current HEAD without creating worktrees there. Pass
--freshto delete and re-clone.package.json) fingerprint changes, or whennode_modulesis missing. A marker under.asil-scratch/records the last bootstrap.--interval SECrepeats grind in one process after sleeping. It implies--skip-questions. SIGINT/SIGTERM stop the loop and leave the warm scratch on disk.Test plan
pnpm typecheckpnpm test--freshdeletes the warm scratch before cloningnode_modulesskips install and recursive build--intervalforces--skip-questions; invalid values are rejectedinterruptibleSleepreturns early when stop is requested