Team Owners
codeowners.team-owners
Requires at least one team-based owner (@org/team) in the CODEOWNERS file for better ownership continuity.
Compatible Integrations
This guardrail works with the following integrations. Click to see how to use Team Owners with each collector.
Enable This Guardrail
Add the parent policy to your lunar-config.yml to enable this guardrail.
policies:
- uses: github://earthly/lunar-lib/policies/codeowners@v1.0.0
include: [team-owners]
# with: ...How This Guardrail Works
This guardrail is part of the CODEOWNERS Guardrails policy. It evaluates data collected by integrations and produces a pass/fail check with actionable feedback.
When enabled, this check runs automatically on every PR and in AI coding workflows, providing real-time enforcement of your engineering standards.
Learn How Lunar Works →Configuration Options
These inputs can be configured in your lunar-config.yml to customize
how the parent policy (and this guardrail) behaves.
| Input | Required | Default | Description |
|---|---|---|---|
min_owners_per_rule
|
Optional |
2
|
Minimum number of owners required per CODEOWNERS rule (for min-owners check) |
max_owners_per_rule
|
Optional |
10
|
Maximum number of owners allowed per CODEOWNERS rule (for max-owners check) |
CODEOWNERS Guardrails
This guardrail is part of the CODEOWNERS Guardrails policy, which includes 8 guardrails for repository and ownership.
Ready to Automate Your Standards?
See how Lunar can turn your engineering wiki, compliance docs, or postmortem action items into automated guardrails with our 100+ built-in guardrails.
Infrastructure conventions
Post-mortem action items
Security & compliance policies
Testing & quality requirements