Skip to content

Conversation

dougthor42
Copy link
Collaborator

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:

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.

@dougthor42 dougthor42 changed the title (fix:gazelle) Do not build proto targets with default Gazelle fix(gazelle): Do not build proto targets with default Gazelle Aug 26, 2025
@dougthor42 dougthor42 marked this pull request as ready for review August 26, 2025 20:45
@dougthor42 dougthor42 added this pull request to the merge queue Aug 27, 2025
@dougthor42
Copy link
Collaborator Author

@rickeylev or @aignas: Do I need to merge this PR into the 1.6rc0 branch? ie: what's the release process for fixes after a RC branch has been made?

Merged via the queue into bazel-contrib:main with commit 2ed714f Aug 27, 2025
3 checks passed
@dougthor42 dougthor42 deleted the u/dthor/no-proto-gh3209 branch August 27, 2025 02:59
@aignas aignas mentioned this pull request Aug 27, 2025
9 tasks
aignas pushed a commit that referenced this pull request Sep 8, 2025
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 2ed714f)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants