ci(crow): add weekly patch-proposal + feedback-loop pipeline #118
Loading…
Reference in a new issue
No description provided.
Delete branch "t3code/crow-weekly-patch-proposals"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds the scheduled pipeline for the failure-triage proposer/tracker landed in #117 (issue #115, steps 3 + 4).
.crow/weekly-patch-proposals.yamlA single (non-matrix) job -- the classifier groups over all of
single_builds, so unlike the per-platformweekly-audit-missingit runs once globally. Weekly it:propose-patches.R --open-issue-- posts/updates a Forgejo tracking issue with the auto-proposable registry entries (human reviews, trial-builds, opens the PR; nothing merges).proposal-tracking.R-- logs the feedback-loop metrics (signature hit rate, proposed-vs-merged, retirement candidates).Low blast radius: clones read-only (
REPO_RO_TOKEN); the only write is the tracking issue viaFORGEJO_TOKEN. It builds nothing (no B2 keys, no bincraft).Triggers:
cron: weekly-patch-proposals(register the cron in the crow UI) or manual withtask=weekly-patch-proposals, matching thearchive-missed-packagesconvention. Documented under "Scheduled run" inlocal/patches/README.md.yamllintand the other pre-commit hooks pass.