ci(sync): replace branch-protection-bot with github-script - #20
Open
mnencia wants to merge 1 commit into
Open
Conversation
benjefferies/branch-protection-bot is unmaintained and unpinned by digest. Use actions/github-script with the GitHub API directly to toggle the "include administrators" branch protection around the sync push, matching the approach already merged in cloudnative-pg/postgis-containers#139. Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The benjefferies/branch-protection-bot Docker action is not maintained anymore, its build requires a long startup on every run, and it currently fails because it's built on Bullseye which recently went EOL,
Replace it with actions/github-script (Node, no image pull) calling the same enforce_admins REST endpoints.
The restore step now runs only when the disable step recorded enforce_admins as enabled, so the protection is restored even if the protected step failed and is not toggled when it was off to begin with.