generated from coulomb/repo-seed
Implement weekly coding retro schedule
This commit is contained in:
@@ -149,6 +149,26 @@ activity registration issues before the next scheduled run.
|
||||
|
||||
---
|
||||
|
||||
## Weekly maintenance definitions
|
||||
|
||||
`weekly-sbom-staleness` is the canonical rule-only weekly maintenance schedule.
|
||||
It runs Mondays at 09:00 Europe/Berlin, resolves State Hub SBOM status for all
|
||||
repos, and emits one automated task per stale repo through explicit
|
||||
`for_each: context.repos.repos`.
|
||||
|
||||
`weekly-coding-retro` follows the same cron -> context resolver -> per-repo task
|
||||
pattern for coding-session retrospection. It runs Saturdays at 19:00
|
||||
Europe/Berlin and resolves the latest State Hub `/progress/` item with
|
||||
`event_type=coding_retro` into `context.retro.suggestions`. Each positive-score
|
||||
suggestion emits one task to `context.s.repo` with labels
|
||||
`coding-retro`, `improvement`, and `automated`.
|
||||
|
||||
Keep `weekly-coding-retro` disabled until Helix Forge publishes the
|
||||
`coding_retro` read model and a smoke run confirms the resolver returns a
|
||||
non-empty suggestion set with no duplicate target tasks on re-run.
|
||||
|
||||
---
|
||||
|
||||
## Temporal UI — filtering by activity
|
||||
|
||||
With search attributes registered, you can filter in the Temporal Web UI:
|
||||
|
||||
Reference in New Issue
Block a user