Skip to content

chore(codeowners): correct enforcement note and add @aprojic to security files #110

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.

Sign up for GitHub

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

Merged
MDzaja merged 1 commit into from
Jul 31, 2026
Merged

chore(codeowners): correct enforcement note and add @aprojic to security files #110

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions .github/CODEOWNERS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,17 +1,19 @@
# CODEOWNERS -- Daytona
# These owners are automatically requested for review on PRs that modify the listed files.
# Multiple owners = OR semantics (any one can approve).
# Enforcement: the "Security baseline" Ruleset requires CODEOWNERS review on main,
# Enforcement: classic branch protection on main requires code owner review,
# so listed owners must approve before merge.

# Security and compliance policies (CISO-owned)
SECURITY.md @MDzaja
CODE_OF_CONDUCT.md @MDzaja
SECURITY.md @MDzaja @aprojic
CODE_OF_CONDUCT.md @MDzaja @aprojic

# Contributor License Agreement (legal)
CLA.md @MDzaja @aprojic

# CI/CD pipelines and composite actions
# NOTE: job names in pr_checks.yaml and cla.yaml are required status checks on
# main -- renaming a job without updating the branch protection list blocks all merges.
.github/workflows/ @MDzaja
.github/actions/ @MDzaja

Expand Down
Loading