fix(examples): bump gazelle in examples/build_file_generation#1421
fix(examples): bump gazelle in examples/build_file_generation#1421aignas merged 5 commits intobazel-contrib:mainfrom
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
Thanks for the PR @OliverFM, could you please sign the CLA and fix |
Will do! I've been away for the last week, but can fix this sometime in the next few days when I am back with my laptop :) |
|
@aignas I think that this is all sorted – though the CLA change has not showed up yet |
|
@OliverFM It seems that |
7e11dc8 to
5079e51
Compare
…e-generation' into oliver/fix-buildfile-generation
| ) | ||
|
|
||
| # Download the bazel_gazelle ruleset. | ||
| GAZELLE_VERSION = "0.33.0" |
There was a problem hiding this comment.
This is actually a bad refactor, especially to put into examples. Many people use renovate to bump dependencies and it won't understand this. Could you bump the dependency without making this refactor, please?
There was a problem hiding this comment.
Ah I see, I hadn't realised that was why it was setup that way. I will make that change :)
There was a problem hiding this comment.
done -- will rerequest review when CI passes
This is a trivial change now and merging it in order to fix the examples.
…contrib#1421) This PR fixes some broken examples in `examples/build_file_generation` – because `gazelle` needed to be updated. After this PR, `bazel run //:requirements.update && bazel run //:gazelle_python_manifest.update && bazel run //:gazelle` no runs. Moreover if you delete the autogenerated sections of the `BUILD.bazel` file, it will regenerate them. Fixes bazel-contrib#1372
This PR fixes some broken examples in
examples/build_file_generation– becausegazelleneeded to be updated.After this PR,
bazel run //:requirements.update && bazel run //:gazelle_python_manifest.update && bazel run //:gazelleno runs. Moreover if you delete the autogenerated sections of theBUILD.bazelfile, it will regenerate them.Fixes #1372