# CodeWarden

> How CodeWarden reviews pull requests on GitHub.com, how to configure it, and what it costs.

- [Introduction](https://docs.codewarden.co/index.md): What CodeWarden does on your pull requests, and what it deliberately does not do.
- [Quickstart](https://docs.codewarden.co/quickstart.md): Install the GitHub App, start the trial, open a pull request, and read your first review.
- [How a review works](https://docs.codewarden.co/how-a-review-works.md): What CodeWarden reads, what it skips, how pushes after the first are handled, and what it posts.
- [.codewarden.yml reference](https://docs.codewarden.co/configure/codewarden-yml.md): Every key of the file a repository uses to tell CodeWarden its own rules: type, default, and an example.
- [Accepted findings](https://docs.codewarden.co/configure/accepted-findings.md): How a finding your team rejected stays rejected: on one pull request, or across the repository with accepted: in .codewarden.yml.
- [Repository switches and excluding pull requests](https://docs.codewarden.co/configure/repositories.md): Choose which repositories CodeWarden reviews, and leave a pull request out of the measurements.
- [Jira](https://docs.codewarden.co/integrations/jira.md): Hold a pull request to the Jira ticket it links: setup, what is read, what is stored, and how to disconnect.
- [Sentry](https://docs.codewarden.co/integrations/sentry.md): Review a fix with the Sentry issue and its stack trace in view: setup, what is read, what is stored, and how to revoke.
- [Talking to CodeWarden](https://docs.codewarden.co/bot/mentions.md): Reply to a CodeWarden comment with @codewardenapp to ask about it, argue with it, or get it to stop raising a finding.
- [Comment categories and severities](https://docs.codewarden.co/bot/categories-and-severities.md): What each category and severity on a CodeWarden comment means, and how they affect what is published.
- [Organizations and roles](https://docs.codewarden.co/console/organizations-and-roles.md): How the console decides who sees an organization, what owners can do that members cannot, and how to sign in.
- [Review history](https://docs.codewarden.co/console/review-history.md): Every review of a repository, what it published, what it dropped and why, and which rules were in force.
- [Measurements](https://docs.codewarden.co/console/measurements.md): How often CodeWarden's comments led to a change in the code, on your own repositories.
- [Activity log](https://docs.codewarden.co/console/activity-log.md): Reviews, replies to mentions and configuration changes in one organization, newest first.
- [Weekly digest](https://docs.codewarden.co/console/weekly-digest.md): The Monday email owners receive about the week before, and how to turn it off.
- [Plans and AI turns](https://docs.codewarden.co/account/plans-and-ai-turns.md): What each plan includes, what an AI turn is, and what happens when the allowance runs out.
- [Trial](https://docs.codewarden.co/account/trial.md): 14 days and 50 AI turns of the full product, with a card on file.
- [Deleting your account or organization data](https://docs.codewarden.co/account/deleting-data.md): Delete your own login at once, or an organization's data after a 7-day window, from the console. What each removes and what is kept.
- [Privacy and security](https://docs.codewarden.co/account/privacy-and-security.md): The short version of how CodeWarden handles your code. The privacy policy is the authoritative text.
- [FAQ](https://docs.codewarden.co/faq.md): Short, honest answers about platforms, languages, cost and what CodeWarden will not do.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.