[8.8.0] Share one RunfilesTreeUpdater per command across spawn strategies
Open
soft-release-blocker
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 72
Description
Forked from #29901
Contributor guide
Research direction
Start by reading the parent issue #29901, then trace how a command uses RunfilesTreeUpdater across its spawn strategies. The issue is complete when one updater is shared per command rather than created separately for each strategy, with the relevant behavior verified by the project's existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100