also looking at this
fix(reports): honour reports.enabled and reports.period, drop the key nothing could read
#1429
7 files
+118
-9
| @@ -226,10 +226,18 @@ export interface BuddyConfig { | ||
| 226 | 226 | * the numbers; it never produces them. |
| 227 | 227 | */ |
| 228 | 228 | reports?: { |
| 229 | /** Generate reports (default: false) */ | |
| 229 | /** | |
| 230 | * Publish the scheduled report (default: false). | |
| 231 | * | |
| 232 | * Governs only the run the generated workflow starts: a cron trigger | |
| 233 | * cannot read this file, so the workflow passes `--scheduled` and the | |
| 234 | * command declines to publish unless this is `true`. A person running | |
| 235 | * `buddy report --publish` by hand has already decided. | |
| 236 | * | |
| 237 | * The cadence itself lives in the workflow's `schedule:` block — there | |
| 238 | * is no config key for it, because nothing at trigger time could read one. | |
| 239 | */ | |
| 230 | 240 | enabled?: boolean |
| 231 | /** Cron expression for the scheduled run */ | |
| 232 | schedule?: string | |
| 233 | 241 | /** Reporting window (default: `30d`) */ |
| 234 | 242 | period?: '7d' | '30d' | '90d' |
| 235 | 243 | /** What the AI narrative should emphasise */ |