Skip to content

Develop: Correct typo from 'pare' to 'parse' in documentation #16860

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lucas-zimerman merged 3 commits into from
Mar 18, 2026
Merged

Develop: Correct typo from 'pare' to 'parse' in documentation #16860

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
86c443e
Develop: Correct typo from 'pare' to 'parse' in documentation
lucas-zimerman Mar 10, 2026
f8fa110
Merge branch 'master' into lz/pare-patch
lucas-zimerman Mar 13, 2026
886909d
Merge branch 'master' into lz/pare-patch
lucas-zimerman Mar 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion develop-docs/engineering-practices/commit-messages.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ sidebar_order: 10

### Merge vs Rebase

Sentry uses a rebase workflow. That means that every commit on its own should be a clear, functional, and stable change. This means that when you’re building a new feature, you should try to pare it down into functional steps, and when that’s not reasonable, the end patch should be a single commit. This is counter to having a Pull Request which may include “fix [unmerged] behavior”. Those commits should be squashed, and the final patch when landed should be rebased.
Sentry uses a rebase workflow. That means that every commit on its own should be a clear, functional, and stable change. This means that when you’re building a new feature, you should try to parse it down into functional steps, and when that’s not reasonable, the end patch should be a single commit. This is counter to having a Pull Request which may include “fix [unmerged] behavior”. Those commits should be squashed, and the final patch when landed should be rebased.

Remember: each commit should follow the commit message format and be stable (green build).

Expand Down
Loading