Workflow runs
Environments not gated
These workflows name an environment:: Deploy configuration site to Bunny, Rebuild and publish IDFM catalog, Roll back Bunny configuration site. Jobs declaring one DO receive that environment's secrets (they override same-named repository secrets), but rickub does not enforce environment protection rules: required reviewers, wait timers and deployment branches do not gate anything, so those jobs run without approval. To gate a deploy, use the secret-presence pattern in the migration guide.
- successDeploy configuration site to Bunny 27d ago
- failureDeploy configuration site to Bunny 27d ago
- failureDeploy configuration site to Bunny 27d ago
- failureDeploy configuration site to Bunny 27d ago
- failureDeploy configuration site to Bunny 27d ago
- failureDeploy configuration site to Bunny 28d ago
- failureDeploy configuration site to Bunny 28d ago
- failureDeploy configuration site to Bunny 28d ago
- failureDeploy configuration site to Bunny 28d ago
- successTests 28d ago
- failureTests 28d ago
- failureDeploy configuration site to Bunny Sep 22, 2026
- failureDeploy configuration site to Bunny Sep 22, 2026
- failureDeploy configuration site to Bunny Sep 22, 2026
- failureDeploy configuration site to Bunny Sep 22, 2026
- failureDeploy configuration site to Bunny Sep 22, 2026
- failureDeploy configuration site to Bunny Sep 22, 2026
- failureDeploy configuration site to Bunny Sep 22, 2026
- failureDeploy configuration site to Bunny Sep 22, 2026