---
title: "Review and CI"
url: https://develop.sentry.dev/sdk/getting-started/standards/review-ci/
---

# Review and CI

This document uses key words such as "MUST", "SHOULD", and "MAY" as defined in

<!-- -->

[RFC 2119](https://www.ietf.org/rfc/rfc2119.txt) to indicate requirement levels.

Statusstable

Version`1.1.0`[(changelog)](https://develop.sentry.dev/sdk/getting-started/standards/review-ci.md#changelog)

These standards cover how code gets reviewed and what CI must check before anything merges or ships. The goal: catch problems early, keep reviews useful, and make sure releases are safe.

## [Code review](https://develop.sentry.dev/sdk/getting-started/standards/review-ci.md#code-review)

Stablespecified since

<!-- -->

1.0.0

### [Who needs to review](https://develop.sentry.dev/sdk/getting-started/standards/review-ci.md#who-needs-to-review)

Every PR **REQUIRES** at least one approving review. Some changes need review from an [SDK Senior Engineer](https://github.com/orgs/getsentry/teams/sdk-seniors):

* [Public API changes](https://develop.sentry.dev/sdk/getting-started/standards/api-architecture.md#public-api-changes)
* [New dependencies](https://develop.sentry.dev/sdk/getting-started/standards/code-quality.md#dependencies)
* [Security-sensitive code](https://develop.sentry.dev/sdk/getting-started/standards/code-quality.md#security)
* Schema changes
* Frameworks or architectural shifts

PRs from external contributors need review from someone with context on the affected area.

### [Turnaround time](https://develop.sentry.dev/sdk/getting-started/standards/review-ci.md#turnaround-time)

Internal PRs should get a first substantive review within 1 business day. External PRs should get a first response within 2 business days. "First review" means real feedback, not just a reaction.

If you're the sole reviewer for an area and don't have capacity, proactively find coverage — another reviewer or AI assist. PR authors should also help identify an appropriate reviewer to avoid blocking.

### [Feedback conventions](https://develop.sentry.dev/sdk/getting-started/standards/review-ci.md#feedback-conventions)

Use the LOGAF scale to signal the weight of your feedback:

* **`h:`** (high) — must fix: bugs, security issues, breakage, data loss
* **`m:`** (medium) — should fix: design, missing tests, clarity
* **`l:`** (low) — optional nit: style, minor suggestions

Comments without a prefix are treated as medium. A PR **MUST NOT** merge with unresolved `h:` comments.

***

## [CI checks](https://develop.sentry.dev/sdk/getting-started/standards/review-ci.md#ci-checks)

Stablespecified since

<!-- -->

1.0.0

Every SDK repo **MUST** have these as required status checks:

1. Build
2. Lint
3. Type check (where applicable)
4. Tests
5. Secret Scanning

These are also recommended but not yet required everywhere:

* Commit message validation
* Size and performance checks
* API snapshot diffs
* Changelog validation

***

## [Warden](https://develop.sentry.dev/sdk/getting-started/standards/review-ci.md#warden)

Stablespecified since

<!-- -->

1.1.0

SDK repos **SHOULD** have [Warden](https://warden.sentry.dev/) configured in CI via the Warden GitHub Action. Warden runs AI-powered skills against PR diffs to enforce SDK-specific conventions that static linters can't express. Which skills are active varies by SDK.

***

## [Release gating](https://develop.sentry.dev/sdk/getting-started/standards/review-ci.md#release-gating)

Stablespecified since

<!-- -->

1.0.0

A release **MUST NOT** ship if:

* Any required CI check fails
* Any `h:` review comment remains unresolved on merged PRs since the last release
* The changelog is empty for user-facing changes
* Any known regression remains unresolved

See [Setting up release infrastructure](https://develop.sentry.dev/sdk/getting-started/playbooks/setup/setting-up-release-infrastructure.md) for initial release setup.

***

## [Changelog](https://develop.sentry.dev/sdk/getting-started/standards/review-ci.md#changelog)

| Version | Date       | Summary                        |
| ------- | ---------- | ------------------------------ |
| `1.1.0` | 2026-03-06 | Add Warden SHOULD requirement  |
| `1.0.0` | 2026-02-19 | Initial Review and CI standard |