From fef124bc1f41f63a6cd4b01552e21820436086dc Mon Sep 17 00:00:00 2001 From: James Rich <2199651+jamesarich@users.noreply.github.com> Date: Mon, 29 Jun 2026 10:28:29 -0500 Subject: [PATCH] fix(docs): stop builds from churning tracked docs screenshots (#6012) Co-authored-by: Claude Opus 4.8 --- feature/docs/build.gradle.kts | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/feature/docs/build.gradle.kts b/feature/docs/build.gradle.kts index b35fcc76f..b39cc766e 100644 --- a/feature/docs/build.gradle.kts +++ b/feature/docs/build.gradle.kts @@ -95,8 +95,12 @@ tasks } .configureEach { dependsOn(syncDocsToComposeResources) } -// FR-038: Ensure screenshots are generated before syncing docs resources -syncDocsToComposeResources.configure { dependsOn(":screenshot-tests:copyDocsScreenshots") } +// ponytail: do NOT wire copyDocsScreenshots into the build. It writes into the tracked +// docs/assets/screenshots/, so a build-time dependsOn rewrote those PNGs on every assemble/test +// run and churned the working tree. The app bundles the committed copies as-is; regenerate on +// demand for local viewing (./gradlew :screenshot-tests:copyDocsScreenshots) and `git checkout` to +// clean, or commit deliberately when refreshing the docs/Jekyll image set. Add a CI staleness gate +// if drift becomes a problem. val syncTranslatedDocsToComposeResources by tasks.registering(Copy::class) {