Switch Glob to rg with fallbacks and backend logging#334
Merged
GCWing merged 1 commit intoGCWing:mainfrom Apr 2, 2026
Merged
Conversation
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
Globlocal execution to preferrg --files --globwhile keeping a Rust walker fallback whenrgis unavailableGlobexecution to preferrgand fall back tofindwhen the remote host does not have ripgrep installedGlobran viarg, remoterg, fallback walker, or remotefindWhy
Globbehavior more closely with the Claude-style ripgrep-backed implementationrgValidation
cargo test -q -p bitfun-core glob_tool