-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to ignore git submodules #23
Comments
How can (Running a |
I'd like to close this. If there's a simple way to detect submodules that doesn't sacrifice performance, I might be willing to support that. One thing I'm worried about is that I personally don't have much experience with submodules, so I don't know whether it's the Right Thing to ignore them or not. My suspicion is yes, it is right, because I tend to see them used as a way to vendor dependencies. |
If it is going to be implemented please make it optional. Internal libraries shared between multiple projects can also be included as submodules. In that case I want to search them too e.g. when performing a global refactoring. |
@BurntSushi there will be a
Here, the |
More importantly, there should be a |
ah that is true too, a |
I think the I think I'd like to ask that you use With that said, if someone submitted a PR to the |
I'm going to close this as part of a process of culling the issue tracker to things that are likely to be implemented. I think my previous comment still stands, but I would still rather not add a new flag and instead just insist that this be part of using ripgrep's |
Would you still be open to a PR on the
If I understand correctly, the idea is just to check for the existence of the standard
|
This implements the suggestion made in BurntSushi#23 to provide an option to ignore nested git repositories. A nested git repository is identified by the presence of a .git file or directory. It's a directory in the regular case, but it's a file for git worktrees and git submodules. This option is disabled by default.
This implements the suggestion made in BurntSushi#23 to provide an option to ignore nested git repositories. A nested git repository is identified by the presence of a .git file or directory. It's a directory in the regular case, but it's a file for git worktrees and git submodules. This option is disabled by default.
This implements the suggestion made in BurntSushi#23 to provide an option to ignore nested git repositories. A nested git repository is identified by the presence of a .git file or directory. It's a directory in the regular case, but it's a file for git worktrees and git submodules. This option is disabled by default.
Helps ripgrep defaults handle them properly while waiting for ripgrep to get submodule support built-in (BurntSushi/ripgrep#23).
Helps ripgrep defaults handle them properly while waiting for ripgrep to get submodule support built-in (BurntSushi/ripgrep#23).
git grep
by default does not search for files within a git submodule, even though they appear like normal directories.rg
on the other hand will by default recurse into these directories.Since
.gitignore
is supported, it would be convenient to support how git searches when there are submodules. (Either by default and turn off with one of the-u
flags, or provide some other flag besides explicitly black listing the submodule folders.)The text was updated successfully, but these errors were encountered: