infamous-riddles/Branch Guardian

Create and/or delete branch protection rules based on a supplied branch pattern.

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stalelast commit Apr 4, 2022
License: MIT
Runtime: Deprecated runtime

Pinned Snippet

workflow.ymlSHA-pinned

uses: infamous-riddles/branch-guardian@4aa8d860752b63edc2ff1ec1c7c74034e471e5e4 # v1

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
BASE-BRANCH-PATTERN	The pattern of the base branch	—	—
PERSONAL-ACCESS-TOKEN	Personal access token to read branch protection rules	—	—
RULES-LIMIT	The number of branch protection rules to check in order to find and delete	—	100
REQUIRED-NUMBER-OF-REVIEWERS	The number of required reviewers when creating a branch protection rule	—	1
REQUIRED-STATUS-CHECKS	The status check that need to be successful before a PR can be merged.	—	—
REQUIRE-REVIEW-FROM-CODEOWNERS	Set to true if you need to require an approved review in pull requests including files with a designated code owner.	—	false
DISMISS-STALE-PR-APPROVALS-ON-NEW-COMMITS	Set to true if you need new reviewable commits pushed to a matching branch to dismiss pull request review approvals.	—	false
REQUIRE-LINEAR-HISTORY	Set to true if you need linear history on your Pull Requests.	—	false
ALLOW-FORCE-PUSHES	Set to true if you want to permit force pushes for all users with push access.	—	false
ALLOW-DELETIONS	Set to true if you want to allow users with push access to delete matching branches.	—	false
INCLUDE-ADMINISTRATORS	Set to true if you want to enforce all configured restrictions for administrators, as well.	—	false
RESTRICTIONS-USERS	List of users allowed to push on the protected branch.	—	""
RESTRICTIONS-TEAMS	List of teams allowed to push on the protected branch.	—	""
RESTRICTIONS-APPS	List of apps allowed to push on the protected branch.	—	""

Outputs

no outputs