Require Private

✓ Guardrail VCS Guardrails Stable Repository And Ownership

vcs.require-private

Ensures repository visibility is set to private, not public. Prevents accidental exposure of proprietary code.

private repository visibility

Get Started View All VCS Guardrails

Compatible Integrations

This guardrail works with the following integrations. Click to see how to use Require Private with each collector.

Require Private + GitHub Collector Provides repository and branch protection data

→

Require Private + GitLab Collector Provides repository and branch protection data

→

Enable This Guardrail

Add the parent policy to your lunar-config.yml to enable this guardrail.

📄 lunar-config.yml

policies:
  - uses: github://earthly/lunar-lib/policies/vcs@v1.0.5
    include: [require-private]
    # with: ...

How This Guardrail Works

This guardrail is part of the VCS 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 →

↓ Integrations Gather Data

Collectors extract metadata from code, CI pipelines, tool outputs, and scans

{ } Centralized as JSON

All data merged into each component's unified metadata document

✓ This Guardrail Checks Current

Require Private runs and provides pass/fail feedback

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_approvals`	Optional	`1`	Minimum number of required approvals (integer, or omit to skip check)
`required_default_branch`	Optional	`main`	Required default branch name for the require-default-branch policy. Defaults to 'main'
`allowed_merge_strategies`	Required	—	Comma-separated list of allowed merge strategies for the allowed-merge-strategies policy (merge, squash, rebase). Only listed strategies will be allowed
`allowed_bypass_actors`	Required	—	Bypass actors the disallow-bypass-actors check accepts, one per line or comma-separated. An entry is an actor type (`OrganizationAdmin`, `DeployKey`) or `<type>:<id>`: a ruleset bypass actor's `actor_id` (`Integration:98765`, `RepositoryRole:5`), or a classic bypass allowance's login or slug (`User:jdoe`, `Team:release-managers`, `Integration:release-bot`). `#` comments out the rest of a line: ```yaml with: allowed_bypass_actors: \| Integration:98765 # release app, tags after CI passes ```

VCS Guardrails

This guardrail is part of the VCS Guardrails policy, which includes 17 guardrails for repository and ownership.

View Policy

Ready to Automate Your Standards?

See how Lunar can turn your AGENTS.md, engineering wiki, compliance docs, or postmortem action items into automated guardrails with our 300+ built-in guardrails.

Works with any process

AI agent rules & prompt files

Post-mortem action items

Security & compliance policies

Testing & quality requirements

Auto-ID My Guardrails

Paste your AGENTS.md or manual process doc and get guardrails in minutes

Book a Demo