Thanks to visit codestin.com
Credit goes to github.com

Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: bazel-contrib/rules_python
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 1.6.0
Choose a base ref
...
head repository: bazel-contrib/rules_python
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 1.6.1
Choose a head ref
  • 1 commit
  • 4 files changed
  • 1 contributor

Commits on Sep 8, 2025

  1. 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 2ed714f)
    @dougthor42 @aignas
    dougthor42 authored and aignas committed Sep 8, 2025
    Configuration menu
    Copy the full SHA
    eed1690 View commit details
    Browse the repository at this point in the history
Loading