Skip to content

The bug of git scan #46617

Description

@husheng876

Description

  1. Silent ignore-filtering in file search glob/grep are ripgrep-backed and silently exclude everything covered by .gitignore. Results carry no indicator that paths were filtered out, so "no matches" is indistinguishable from "the files don't exist". A transparency defect: my view of the repo was filtered without either of us knowing.

  2. Git-state analysis never loaded ignore rules During the repo audit I ran git status and classified untracked files without ever reading .gitignore, conflating three distinct categories: deliberately-local paths (.env, thought_review/**), genuinely uncommitted work (the agent_interview batch), and pure junk (0-byte account/usage). This was the root cause of your "I already pushed, why does it still show changes" confusion.

Plugins

No response

OpenCode version

1.18.25

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

Windows10

Terminal

No response

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions