Skip to content

ci: add CODEOWNERS + require code-owner review - #91

Merged
tonibergholm merged 1 commit into
mainfrom
ci/codeowners
Jul 18, 2026
Merged

tonibergholm merged 1 commit into
mainfrom
ci/codeowners

Conversation

@tonibergholm

Copy link
Copy Markdown
Member

Adds .github/CODEOWNERS (both admins own everything, with explicit callouts for crates/crypto, crates/tlsio, .github, and the security docs) and enables require_code_owner_review on the main ruleset (set live, verified).

Closes the one residual Scorecard BranchProtection sub-item — "codeowners review is not required" — leaving the optional OpenSSF badge as the only open code-scanning finding.

Supersedes #90, which auto-closed when its stacked base (#89) merged and its branch was deleted. Rebased onto current main; needs the other admin's approval to merge (and, once this lands, code-owner review too).

…rotection residual

.github/CODEOWNERS names both admin accounts as owners of everything,
with explicit callouts for crypto/tlsio, .github, and the security docs.
The main ruleset's require_code_owner_review is now true (set live).

This closes the one residual Scorecard BranchProtection sub-item
('codeowners review is not required'); the only remaining open
code-scanning finding is the optional OpenSSF badge.

Stacked on #89 (required-review docs). Updates ACCESS.md,
opsec-baseline.md, and the fifth-round evidence delta.
@tonibergholm
tonibergholm merged commit 7ff9ecd into main Jul 18, 2026
7 checks passed
@tonibergholm
tonibergholm deleted the ci/codeowners branch July 18, 2026 10:40
tonibergholm added a commit that referenced this pull request Jul 18, 2026
…aps (#92)

After the re-scan on the #91 merge commit, the honest picture:
- BranchProtection 3->8/10 (config complete; top 2 pts need >=2 reviewers,
  impractical for a 2-person team).
- CodeReview still 0 — a trailing 'N/25 approved changesets' history
  metric that self-heals as reviewed PRs accumulate, not a config switch.
- CIIBestPractices — optional OpenSSF badge.

Corrects the fifth-round projection that #4/#14 would 'clear on next
scan': the configuration completed, but these two persist as a team-size
scoring cap and a self-healing metric. G-032/T-16 is closed either way.
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.

2 participants