Glob searches can surface ignored files

Problem

Glob documents that it respects .gitignore, .ignore, and .rgignore by default, but broad patterns can return ignored files.

Two ripgrep behaviors cause this:

• Broad patterns such as *, **, and **/* are passed as positive --glob filters. Positive ripgrep globs can re-include files that ignore rules would otherwise exclude.
• Ripgrep only applies .gitignore outside git repositories when --no-require-git is set. Glob does not currently pass that flag for non-git search roots.

Reproduction

In a directory with:

.gitignore   # contains *.log
kept.ts
ignored.log

Run Glob with pattern: "*".

Expected

kept.ts is returned and ignored.log is excluded by .gitignore.

Actual

ignored.log can be returned, including in a git repo when the broad pattern is emitted as a positive --glob, and in non-git directories because .gitignore is not honored without --no-require-git.

Notes

Useful reference patterns:

• opencode avoids a positive glob for broad discovery in its find path.
• pi walks upward for .git and uses --no-require-git outside repos.

Start at the TypeScript Glob entry point and trace how broad patterns become ripgrep arguments; run the provided reproduction in both a Git repository and a non-Git directory. Done means kept.ts is returned while ignored.log is excluded by .gitignore for broad patterns such as *.