create-pr

Topics in the source

• Create Pull Request
• Process
• Step 1: Verify Branch State
• Step 2: Analyze Changes
• Step 3: Write the PR Description
• Step 4: Create the PR
• Step 5: Add Reviewers (if known)
• PR Description Examples

Create pull requests following Sentry's engineering practices. Requires: GitHub CLI (gh) authenticated and available. Ensure: All changes are committed Branch is up to date with remote Changes are rebased on main if needed Review what will be included in the PR: Understand the scope and purpose of all changes before writing the description. Follow this structure: Do NOT include: "Test plan" sections Checkbox lists of testing steps Redundant summaries of the diff Do include: Clear explanation of what and why Links to relevant issues or tickets Context that isn't obvious from the code Notes on specific areas that need careful review Title format follows commit conventions: feat(scope): Add new feature fix(scope): Fix the bug ref: Refactor something Limit to 1-3 reviewers to maintain clear ownership. Reference issues in the PR body: | Syntax | Effect | |--------|--------| | Fixes #1234 | Closes GitHub issue on merge | | Fixes SENTRY-1234 | Closes Sentry issue | | Refs GH-1234 | Links without closing | | Refs LINEAR-ABC-123 | Links Linear issue | One PR per feature/fix - Don't bundle unrelated changes Keep PRs reviewable - Smaller PRs get faster, better reviews Explain the why - Code s

This is an excerpt. Refer to the complete source and its current requirements.