fix: rescan (r) now performs fresh scan instead of returning cached data #13
+13
−11
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
r) to bypass cache and fetch fresh git statusProblem
When pressing
rto rescan, the app callsscanReposCmd()which checks cache first. If the cache is valid (< 5 min) and roots haven't changed, it returns stale data. Users had to quit and restart the app to see updated dirty/clean status.Solution
Added
forceRefresh boolparameter toscanReposCmd():r(rescan) and workspace switch now passtrueto bypass cachefalseto benefit from fast cached startupTest plan
git-scope, note a repo's statustouch newfile)rto rescan — status should update immediately🤖 Generated with Claude Code