x/tools/imports: should not scan bazel-out directories #35914
What did you do?
Open our monolith repository in VS Code, then open a go file and wait.
What did you expect to see?
What did you see instead?
The CPU usage goes up periodically due to gopls.
By inspecting the file opened by
The text was updated successfully, but these errors were encountered:
Concretely, I'd suggest that the main module, and any replace targets, could contain a
@vincepri, would that work for you as well? It would mean checking in a bunch of
For now, the workaround that we will probably have to do for our monorepo is to move our top-level
I think for multi-language repositories having some way to ignore certain directories by all go tools is a must have! The case of node_modules was discussed multiple times in many different issues, but seems like people were unable to agree on a solution.
@robpike didn't want to create more dot files, so being able to configure this in