Follow-up from PR #16. The two setup/ scripts could not be executed from the remote session that authored the PR: they require the GitHub CLI authenticated with admin on the repo, and that environment has no gh and no API route for rulesets/security settings (both scripts exit 1 at their fail-fast guard, as designed).
Remaining work (run locally, after #16 merges)
pwsh -NoProfile -File setup/Protect-MainBranch.ps1
pwsh -NoProfile -File setup/Enable-RepoSecurity.ps1
Acceptance
Follow-up from PR #16. The two
setup/scripts could not be executed from the remote session that authored the PR: they require the GitHub CLI authenticated with admin on the repo, and that environment has noghand no API route for rulesets/security settings (both scripts exit 1 at their fail-fast guard, as designed).Remaining work (run locally, after #16 merges)
main-protectionruleset carries the newmin_entries_to_merge_wait_minutes = 1(PR Reduce merge-queue wait to 1 min; add MIGRATION.md entry doc + .vscode README #16 changed it from 5).main-protectionruleset already exists, the script will fail on the POST — instead update the existing ruleset's merge-queue wait to 1 min in Settings → Rules (or delete and recreate via the script).Enable-RepoSecurity.ps1is idempotent; plan-restricted settings warn and are skipped.setup/README.md: once protection is active, delete thesetup/folder (template guidance — optional for this template repo itself, since downstream repos still need the scripts).Acceptance
main-protectionruleset active on the default branch with merge-queue wait = 1 min