From 95f95acdb551168f2e5a52e000ff62167be266a8 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 21 Sep 2026 19:18:56 +0000 Subject: gradle-report: name UP-TO-DATE as the cause of a stale report Found by running it: detekt exited 0 while the report predated the run, because Gradle skipped the task. 'STALE' alone leaves the reader to work out why nothing changed, so it now says which task was skipped and how to force it, with --allow-stale to accept an older report deliberately. Same shape as gradle-test, which learned this first. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index a41b312..eff764a 100644 --- a/README.md +++ b/README.md @@ -103,7 +103,7 @@ code that no longer exists — which is exactly what happened three times in one session, the giveaway being line numbers that never moved after a refactor. ``` -gradle-report /workspace/listen detekt +gradle-report /workspace/listen detekt -- --rerun-tasks ``` Prints `CONFIG INVALID` and names the offending property when the config is -- cgit v1.2.3