Skip to content

Conversation

@vivster7
Copy link

PR Instructions/requirements

  • Title uses type: description format. See CONTRIBUTING.md for types.
    • Common types are: build, docs, feat, fix, refactor, revert, test
    • Update CHANGELOG.md as applicable
  • Breaking changes include "!" after the type and a "BREAKING CHANGES:"
    section at the bottom.
    See CONTRIBUTING.md for our breaking changes process.
  • Body text describes:
    • Why this change is being made, briefly.
    • Before and after behavior, as applicable
    • References issue number, as applicable
  • Update docs and tests, as applicable
  • Delete these instructions prior to sending the PR

Vivek Dasari and others added 12 commits July 8, 2025 12:02
When using per-file generation mode, Gazelle was not correctly
updating existing py_library targets that spanned multiple source
files if those files were also processed individually. This change
ensures that such existing targets are re-evaluated as a whole,
allowing their dependencies to be correctly updated.

The test case `per_file_respect_existing_multiple_srcs` now passes
functionally (dependencies are added correctly). A remaining diff
exists due to attribute reordering (tags vs deps) and srcs formatting,
which is a common canonicalization effect and not a functional issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants