GitHub

​

Installation

Install the Zenable GitHub Reviewer here: GitHub Reviewer

​

How It Works

The Zenable GitHub Reviewer automatically reviews pull requests in your repository, providing valuable feedback on code quality, security, and best practices. It leverages any Policy as Code or context you’ve configured in your tenant on zenable.app, ensuring consistent enforcement across your entire development workflow. Once installed, it will:

1. Monitor PR events - Responds to pull request opens, updates, and review requests
2. Analyze code changes - Reviews modified files against your custom policies and organizational context
3. Provide inline feedback - Adds comments directly on the code with specific suggestions
4. Maintain standards - Ensures consistent code quality across your team

​

Re-requesting a Review

You can trigger a new review at any time by commenting /zenable on your pull request. This is useful when:

• You’ve made changes and want fresh feedback
• You want to re-run the review after updating your policies
• The initial review was skipped due to rate limits or other conditions

Simply add a comment with /zenable anywhere in the PR, and Zenable will perform a complete review of the current state of the pull request.

​

Repository Custom Properties

Zenable reads your organization’s repository custom properties — the key/value metadata your org defines centrally, like team, tier, or compliance — and keeps them in sync automatically on installation, when repository access or property values change, and from repository metadata included in pull request events. They power two features:

• Metadata-based scopes — requirements and context that apply only to repos with matching properties (see Repository Metadata Conditions)
• Automatic configuration profile assignment — profiles that attach themselves to matching repos (see Automatic Profile Assignment)

This uses the GitHub App’s organization-level Custom properties (read-only) permission for bulk synchronization. The app also requests repository-level Custom properties (read and write) so property values can be managed at repository scope when the organization’s property definition allows repository actors to edit them. Organizations that installed the app before either permission was added will be prompted by GitHub to approve the update; everything else keeps working in the meantime, and property syncing starts once the organization permission is granted.

​

Unified Context Across All Integration Points

All Zenable integration points (GitHub, GitLab, MCP, API) share the same context and policies from your Zenable tenant. This provides continuous enforcement throughout the entire SDLC - consistently reinforced and fully automated. Whether developers are using AI tools locally, committing code, or creating pull requests, the same standards and policies apply everywhere.

​

Next Steps

After installation, you can:

• Configure the reviewer to match your team’s standards
• Set up pre-commit hooks for developer-side enforcement
• Install the MCP server for real-time IDE feedback
• Define custom policies specific to your organization
• Review our deployment guide for team adoption strategies
• Explore supply chain security to protect your dependencies
• Check our Roadmap to see what’s coming next