Problem
Required-check names on protected branches are derived from generated callback job IDs (validate, build_<name>, deploy_<name>, etc.). Adopters guess at the exact names and apply via gh api manually, with rules drifting from generator output over time as callbacks rename or restructure.
Proposed
Add cascade generate branch-protection --env <env> (or similar) that emits a JSON payload suitable for:
gh api -X PUT repos/<repo>/branches/<branch>/protection --input -
Payload includes required-check names sourced directly from the generator's job IDs, with sensible defaults for review counts / linear history / signed commits etc.
Impact
Removes the "what's the check name today?" guess. Protection rules stay in sync with generator output across upgrades. Additive, zero schema risk — lands post-1.0.
Problem
Required-check names on protected branches are derived from generated callback job IDs (
validate,build_<name>,deploy_<name>, etc.). Adopters guess at the exact names and apply viagh apimanually, with rules drifting from generator output over time as callbacks rename or restructure.Proposed
Add
cascade generate branch-protection --env <env>(or similar) that emits a JSON payload suitable for:Payload includes required-check names sourced directly from the generator's job IDs, with sensible defaults for review counts / linear history / signed commits etc.
Impact
Removes the "what's the check name today?" guess. Protection rules stay in sync with generator output across upgrades. Additive, zero schema risk — lands post-1.0.