the-nexus/CONTRIBUTING.md

Branch Protection & Code Review Policy

Effective immediately for all repositories

Core Requirements

1. All changes must use Pull Requests

   • Direct pushes to main are prohibited

2. Minimum Review Requirements

   • 1+ approvals required to merge
   • @perplexity must be notified for review
   • Original author cannot approve their own PR

3. CI/CD Requirements

   • All CI pipelines must pass before merge
   • No merging of failing builds
   • No force-pushing to protected branches

Repository-Specific Rules

hermes-agent

• 1+ approvals required
• CI/CD pipeline must pass
• No force pushes
• No branch deletion

the-nexus

• 1+ approvals required
• CI/CD pipeline (pending restoration)
• No force pushes
• No branch deletion

timmy-home

• 1+ approvals required
• No CI/CD requirements
• No force pushes
• No branch deletion

timmy-config

• 1+ approvals required
• Limited CI/CD
• No force pushes
• No branch deletion

Enforcement

• Gitea branch protection rules are enabled for all repositories
• Violations will be blocked at merge time
• Exceptions require org admin approval

Reviewer Assignments

• Default reviewer: @perplexity (QA gate)
• Owner reviewer: @Timmy (hermes-agent)
• Specialized owners for domain-specific changes

Compliance

This document is maintained in the main branch of each repository. Policy violations will be addressed through:

1. Automated branch protection rules
2. Manual code owner notifications
3. Org-level audit reviews quarterly

Last updated: 2026-04-07