The release-docs workflow (#82) force-pushes to release-docs/<version> branches on every dispatch. We should configure a branch protection ruleset on release-docs/* so that:
- Only the
openemr-release-bot App can push (everyone else is blocked from accidental pushes that the workflow would just clobber on the next dispatch).
- Direct deletion is restricted (the workflow itself doesn't need to delete branches).
- PR review requirements (if any) explicitly opt out for these refs — they are the output of automation, not human-authored.
This is repo administration, not code, so it lands separately from #82. Worth pairing with the rollout of the docs workflow so the first regeneration doesn't race on an unprotected ref.
References: #82 review thread on .github/workflows/release-docs.yml.
The release-docs workflow (
#82) force-pushes torelease-docs/<version>branches on every dispatch. We should configure a branch protection ruleset onrelease-docs/*so that:openemr-release-botApp can push (everyone else is blocked from accidental pushes that the workflow would just clobber on the next dispatch).This is repo administration, not code, so it lands separately from #82. Worth pairing with the rollout of the docs workflow so the first regeneration doesn't race on an unprotected ref.
References: #82 review thread on
.github/workflows/release-docs.yml.