also looking at this
fix(reports): honour reports.enabled and reports.period, drop the key nothing could read
#1429
7 files
+118
-9
| @@ -315,12 +315,9 @@ Scheduled dependency-health and activity reports. | ||
| 315 | 315 | |
| 316 | 316 | ```typescript |
| 317 | 317 | interface ReportSettings { |
| 318 | /** Generate reports (default: false) */ | |
| 318 | /** Publish the scheduled report (default: false) */ | |
| 319 | 319 | enabled?: boolean |
| 320 | 320 | |
| 321 | /** Cron expression for the scheduled run */ | |
| 322 | schedule?: string | |
| 323 | ||
| 324 | 321 | /** Reporting window (default: `30d`) */ |
| 325 | 322 | period?: '7d' | '30d' | '90d' |
| 326 | 323 | |
| @@ -339,6 +336,13 @@ The report is computed from scan results and pull request history, so it works | ||
| 339 | 336 | with no AI provider. A configured provider adds a narrative around the |
| 340 | 337 | numbers; it never produces them. |
| 341 | 338 | |
| 339 | `enabled` governs only the run the generated workflow starts — a cron trigger | |
| 340 | cannot read this file, so the workflow passes `--scheduled` and the command | |
| 341 | declines to publish unless it is `true`. Running `buddy report --publish` by | |
| 342 | hand publishes regardless. The cadence lives in the workflow's `schedule:` | |
| 343 | block; there is no config key for it, because nothing at trigger time could | |
| 344 | read one. | |
| 345 | ||
| 342 | 346 | ## Analysis |
| 343 | 347 | |
| 344 | 348 | ```typescript |