GitHub Community
Can I configure the file finder to index directories named "build"? #23575
-
|
Today, the GitHub file finder doesn’t find files in directories named “build”. You can see for yourself by viewing this repo and pressing “t”. The file finder only finds “notbuild/foo.txt”, not “build/foo.txt”. Is there a way to configure the file finder to index build? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
|
I wish there was a way to fix this, too. I reached out to support about this recently and was told the following.
From the github help, it looks like this also applies to other folder names too:
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @evankroske, Thanks for the report! Currently, the file finder intentionally excludes directories that commonly contain generated files, including That said, we know that these directories can be important in some cases, and we do have an open feature request to allow the exclusions to be configured. Although I can’t say if or when that feature will be added, I’ll add your report to the feature request, and it’ll be evaluated by our product engineering teams. |
Beta Was this translation helpful? Give feedback.
-
|
This is such a weird opinionated and hidden decision. Where can we “upvote” this feature request? |
Beta Was this translation helpful? Give feedback.
-
|
Idiomatic golang repository structure places build configuration files into the build directory. If you're not willing to make this configurable, is there a chance you can have the file finder indexer add |
Beta Was this translation helpful? Give feedback.
I wish there was a way to fix this, too. I reached out to support about this recently and was told the following.
From the github help, it looks like this also applies to other folder names too: