Skip to content

ci: treat Branch-Protection as a one-maintainer Scorecard residual - #44

Merged
agjs merged 1 commit into
mainfrom
fix/single-maintainer-reviews
Aug 22, 2026
Merged

ci: treat Branch-Protection as a one-maintainer Scorecard residual#44
agjs merged 1 commit into
mainfrom
fix/single-maintainer-reviews

Conversation

@agjs

@agjs agjs commented Aug 22, 2026

Copy link
Copy Markdown
Collaborator

Summary

This org has one maintainer. We cannot require two human reviewers.

Live main protection stays at 1 required review, CODEOWNERS @agjs, last-push approval, enforce_admins, and a maintainer bypass so that one person can still merge.

Scorecard's Branch-Protection check wants two reviewers for a 10. That is not a gate we can satisfy with current headcount. This PR adds BranchProtectionID to the same code-scanning residual filter as Code-Review / CII / SAST / CI-Tests / Fuzzing, so the weekly Scorecard upload does not reopen it.

Full results still publish to scorecard.dev.

Test plan

  • Confirm live protection: required_approving_review_count = 1, bypass agjs
  • After merge, Scorecard workflow upload does not open a Branch-Protection code-scanning alert

A second human reviewer is not available in this org. Keep the live
gate at one review plus the maintainer bypass, and strip
BranchProtectionID from the code-scanning upload so weekly Scorecard
does not reopen it.
@agjs
agjs merged commit 46cd1ac into main Aug 22, 2026
11 checks passed
@agjs
agjs deleted the fix/single-maintainer-reviews branch August 22, 2026 20:51
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.

1 participant