Hey Strider,
Your logic is quite reasonable—if the cache folder contains information like task traces that enable incremental builds, it makes sense to consider putting it in source control so other machines can leverage it.
However, there are a couple of issues with this approach. The cache keeps track of changes since the last build to avoid rebuilding everything from scratch. This data is specific to the local environment and may not be useful across different environments or users.
Additionally, the primary purpose of the cache is to improve build performance rather than ensure build reproducibility. This suggests that it shouldn't be shared or versioned. Builds should be reproducible from the source files and build scripts alone, without relying on cached data.
I hope this makes sense!
