summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorClaude <noreply@anthropic.com>2026-09-21 19:18:56 +0000
committerClaude <noreply@anthropic.com>2026-09-21 19:18:56 +0000
commit95f95acdb551168f2e5a52e000ff62167be266a8 (patch)
treeeb36f1d9fab024f223a988e1815012c1a2a18e35 /README.md
parent8f94e3caa0b1b477bacbbbd8954f2cea743a9337 (diff)
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 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
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