Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

Sentry Commit Messages Follow these conventions when creating commits for Sentry projects. Format The header is required. Scope is optional. All lines must stay under 100 characters. Commit Types Type Purpose feat New feature fix Bug fix ref Refactoring (no behavior change) perf Performance improvement docs Documentation only test Test additions or corrections build Build system or dependencies ci CI configuration chore Maintenance tasks style Code formatting (no logic change) meta Repository metadata license License changes Subject Line Rules Use imperative, present tense: "Add feature" not "Added feature" Capitalize the first letter No period at the end Maximum 70 characters Body Guidelines Explain what and why , not how Use imperative mood and present tense Include motivation for the change Contrast with previous behavior when relevant Footer: Issue References Reference issues in the footer using these patterns: Fixes closes the issue when merged Refs links without closing Examples Simple fix Feature with scope Refactor Breaking change Revert Format Principles Each commit should be a single, stable change Commits should be independently reviewable The repository should be in a working state after each commit References [Sentry Commit Messages](https://develop.sentry.dev/engineering practices/commit messages/)