FAILED: Repository Linter Issue: rl-branch_protection

Open Beginner friendly
#215 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github
Domain
devops, security

Research direction

Start with the default branch protection settings for main and compare them with the rl-branch_protection requirements and the linked GitHub Hardening Controls documentation. Enable approval of the most recent reviewable push and conversation resolution, then verify that the linter no longer reports this violation.

Written by the indexing model from the issue text.

Description

A violation against the SAP Open Source standards have been detected.

Rule: rl-branch_protection

Message: Default branch 'main' protection is incomplete. Missing or incorrectly configured controls:

  • Require approval of the most recent reviewable push
  • Require conversation resolution before merging

Protection method detected: Classic branch protection

Description: Checks if the default branch is protected with either classic branch protection rules or rulesets. Verifies that mandatory security controls are enabled: pull request requirement, minimum 1 approval, dismiss stale reviews, review of latest push, conversation resolution, force push blocking, and deletion restrictions.

Documentation

Dominant language
Go
Stars
1
Forks
10
Avg merge
5d 7h
Merged PRs (30d)
9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from kyma-project/rt-bootstrapper

All issues in kyma-project/rt-bootstrapper

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.