FAILED: Repository Linter Issue: rl-branch_protection
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 43
- Forks
- 22
- Avg merge
- 16h 25m
- Merged PRs (30d)
- 59
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked SAP Open Source standards documentation and the repository's GitHub branch protection settings for the default branch, main. Enable approval of the most recent reviewable push and conversation resolution, then verify that the rl-branch_protection violation is cleared.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100