Repository remediation
Connect GitHub repositories, index code read-only, map findings to code and create customer-approved PRs safely.
Developers and repository admins
Feature availability
Product, package, provider and deployment boundaries for this page.
- Available from
- Current documentation
- Providers
- githubgithub-enterprise
- Deployment modes
- cloudself-hosted
Product screenshots
Current customer-safe screenshots are generated from the application so examples do not drift from the product.
Repository remediation path
Use this section when a customer wants review-only repository remediation from report findings. 
- GitHub repository connection
- GitHub Enterprise considerations
- Read-only indexing
- Code mapping
- Review-only patches
- Customer approval and PR creation
- Revoke and no-secret boundaries
Approval and revoke path
Open `/reports/{report}` before repository work. Connect GitHub only through the product flow, keep indexing read-only until approval, create review-only patches, then require customer approval before `/fix-tasks/{fixTask}/pull-request`.
- Revoke access from [Settings](/settings).
- Never paste repository tokens or private keys into docs, tickets, logs or report copy.
- Use ticket-only fallback when repository access is not approved.
What to open next
- Use [GitHub repository connection](/docs/repository-remediation/github-repository-connection) for setup.
- Use [Review-only patches](/docs/repository-remediation/review-only-patches) before PR creation.
- Use [Revoke and no-secret boundaries](/docs/repository-remediation/revoke-and-no-secret-boundaries) before sharing any remediation output.
Was this page helpful?
Feedback goes into the product documentation review queue.