refactor: remove gazelle plugin as dev dependency#3436
Merged
rickeylev merged 2 commits intobazel-contrib:mainfrom Nov 26, 2025
Merged
refactor: remove gazelle plugin as dev dependency#3436rickeylev merged 2 commits intobazel-contrib:mainfrom
rickeylev merged 2 commits intobazel-contrib:mainfrom
Conversation
rickeylev
force-pushed
the
chore.gazelle.uncoupling
branch
from
867a0cf to
9c1e837
Compare
rickeylev
changed the title
aignas
approved these changes
Nov 26, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove the gazelle pluging as a dev-time dependency of rules_python itself.
This is to avoid gazelle-related build issues that affect the main build.
The gazelle code paths in tests/integration are removed because they were just
test runners being defined, but weren't actually used with any tests.