tree 2e06b6e0ee04edae89d174172e815a0b215566bc
parent 2918ef9be6016580a527eb25892e083c374d667b
author Douglas Thor <dougthor42@users.noreply.github.com> 1756263116 -0700
committer Ignas Anikevicius <240938+aignas@users.noreply.github.com> 1757336181 +0900

fix(gazelle): Do not build proto targets with default Gazelle (#3216)

Fixes #3209.

Revert the change to `//:gazelle_binary` so that it once again only
generates python code. We then create a new, private target
`//:_gazelle_binary_with_proto` that gets used by tests.

Update docs accordingly.

Longer term, I'd like to adjust the `test.yaml` file to include a
section:

```yaml
config:
  gazelle_binary: _gazelle_binary_with_proto
```

So that test cases that need to generate `(py_)proto_library` targets
can use the multi-lang Gazelle binary and that tests that do _not_ need
to generate proto targets can use the single-lang Gazelle binary.

However, there were some minor roadblocks in doing so and thus I'm doing
this quick-to-implement method instead.

(cherry picked from commit 2ed714f9bd3c7df8c1de351455fb8d8d340f76e4)