Skip to content

feat(itg): support excluded file regexes in incremental hash computation - #317

Open
yushan8 wants to merge 1 commit into
mainfrom
itg-excluded-regex
Open

yushan8 wants to merge 1 commit into
mainfrom
itg-excluded-regex

Conversation

@yushan8

@yushan8 yushan8 commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Targets whose name matches one of the configured exclusion regexes now get an empty hash instead of being computed, mirroring the existing isExcluded behavior in core/targethasher/graph.go used by the full-graph hashing path. UpdateGraphInput gains an ExcludedRegex field that is threaded through computeAvailableHashes and the recursive computeHashes/computeInvalidatedHashes so incremental updates respect the same exclusions as a full recompute, and excluded targets short-circuit before their dependencies are resolved.

Test Plan

unit test and tested internally

Targets whose name matches one of the configured exclusion regexes now
get an empty hash instead of being computed, mirroring the existing
isExcluded behavior in core/targethasher/graph.go used by the
full-graph hashing path. UpdateGraphInput gains an ExcludedRegex field
that is threaded through computeAvailableHashes and the recursive
computeHashes/computeInvalidatedHashes so incremental updates respect
the same exclusions as a full recompute, and excluded targets
short-circuit before their dependencies are resolved.

Co-Authored-By: Claude Sonnet 5 <ANONYMIZED_EMAIL_ADDRESS_0_4>
@yushan8
yushan8 requested review from a team as code owners September 22, 2026 20:39
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.

1 participant