Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add: Script for checking the presence of branch protection #973

Merged
merged 1 commit into from
Feb 2, 2024

Conversation

wiegandm
Copy link
Member

@wiegandm wiegandm commented Feb 2, 2024

What

This script is intended to support compliance checks for GitHub repositories regarding requirements on branch protection.

Note that the current implementation only verifies whether branch protection exists at all and does not verify individual branch protection setting which may be required by compliance policies.

Why

To extend the usefulness of pontos for policy compliance checks and intergration.

@wiegandm wiegandm requested a review from a team as a code owner February 2, 2024 10:48
@greenbonebot greenbonebot enabled auto-merge (rebase) February 2, 2024 10:48
Copy link

github-actions bot commented Feb 2, 2024

Conventional Commits Report

Type Number
Added 1

🚀 Conventional commits found.

This script is intended to support compliance checks for GitHub
repositories regarding requirements on branch protection.

Note that the current implementation only verifies whether branch
protection *exists at all* and does not verify individual branch
protection setting which may be required by compliance policies.
@bjoernricks bjoernricks force-pushed the branch_protection_check branch from 1928eb2 to db74bd9 Compare February 2, 2024 11:06
@greenbonebot greenbonebot merged commit 1544ce6 into main Feb 2, 2024
18 checks passed
@greenbonebot greenbonebot deleted the branch_protection_check branch February 2, 2024 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants