joshp123 44ae6995de Trigger CI after yolo promotion ... What: - let the yolo promote job dispatch the CI workflow after pushing main - grant the promote job actions:write for workflow_dispatch Why: - GitHub suppresses push-triggered workflows created by GITHUB_TOKEN, so yolo-promoted commits otherwise lack a CI run on the final main SHA Tests: - scripts/check-flake-lock-owners.sh - node scripts/select-openclaw-release.test.mjs - bash -n scripts/update-pins.sh - ruby -e 'require "yaml"; ARGV.each { |f| YAML.load_file(f) }' .github/workflows/*.yml - GITHUB_ACTIONS=true scripts/update-pins.sh select - nix flake show --accept-flake-config Co-authored-by: Codex <noreply@openai.com>		2026-05-07 11:04:00 +02:00
..
ci.yml	ci: update GitHub Actions runtimes	2026-05-05 10:59:39 +02:00
yolo-update.yml	Trigger CI after yolo promotion	2026-05-07 11:04:00 +02:00