Key Benefits
- Version Control: Track all changes via Git history
- Collaboration: Enable team editing with merge controls
- Automation: Enforce policies instantly after sync
- Audit Trails: Link changes to commits/users
- Environment Promotion: Move policies between stages (e.g., dev → prod)
Prerequisites
- GitHub Repository
- Create a repo for policy files (GitHub’s guide)
- Personal Access Token (PAT)
- Generate a classic PAT with repo scope (GitHub’s PAT guide)
Integration Steps
- Start Integration
- Go to Reva:
Integrations > "+ Integration" > Select "GitHub"
- Go to Reva:
- Configure Settings
- Integration Name*: Unique ID (e.g., prod-policies)
- Description: Purpose (e.g., “Core access policies”)
- Connect GitHub
- PAT*: Your github_pat_xxx token
- Email*: PAT-linked email (e.g., user@domain.com)
- Username*: GitHub username (e.g., johndoe)
- Repository URL*: HTTPS link (e.g., https://github.com/yourteam/policies.git)
- Select Branch
- Choose sync branch (e.g., main or dev)
- Activate
- Click Activate (bottom-right corner)
Tip: Use GitHub’s “Protected Branches” feature with Reva to prevent unauthorized policy changes.