> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zenable.io/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub

> Set up the Zenable GitHub Reviewer in your organization

## Installation

Install the Zenable GitHub Reviewer here: [GitHub Reviewer](https://zenable.io/github?utm_source=docs\&utm_medium=github-integration\&utm_content=install)

<iframe width="560" height="315" src="https://www.youtube.com/embed/ZL9SwLKfu5c?si=dyUOwQBgbDVai_Lk" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen />

## 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](https://www.zenable.app?utm_source=docs\&utm_medium=github-integration\&utm_content=tenant-config), 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.

### 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](/integrations/vcs-reviewers/configuration) to match your team's standards
* Set up [pre-commit hooks](/integrations/pre-commit/getting-started) for developer-side enforcement
* Install the [MCP server](/integrations/mcp/getting-started) for real-time IDE feedback
* Define [custom policies](/use-cases/policy-as-code) specific to your organization
* Review our [deployment guide](/deployment-adoption) for team adoption strategies
* Explore [supply chain security](/use-cases/supply-chain-security) to protect your dependencies
* Check our [Roadmap](https://zenable.io/feedback?utm_source=docs\&utm_medium=github-integration\&utm_content=roadmap) to see what's coming next