Skip to content

meta: Enforce Sentry commit message conventions#2652

Closed
szokeasaurusrex wants to merge 1 commit intoszokeasaurusrex/add-precommitfrom
cursor/implement-phase-one-of-plan-3499
Closed

meta: Enforce Sentry commit message conventions#2652
szokeasaurusrex wants to merge 1 commit intoszokeasaurusrex/add-precommitfrom
cursor/implement-phase-one-of-plan-3499

Conversation

@szokeasaurusrex
Copy link
Copy Markdown
Member

Co-authored-by: daniel.szoke daniel.szoke@sentry.io

Co-authored-by: daniel.szoke <daniel.szoke@sentry.io>
@szokeasaurusrex szokeasaurusrex force-pushed the cursor/implement-phase-one-of-plan-3499 branch from 215b874 to b46a6ab Compare July 25, 2025 12:32
@szokeasaurusrex szokeasaurusrex changed the title meta(dev): Add commit message guidelines and pre-commit validation meta: Enforce Sentry commit message conventions Jul 25, 2025
@szokeasaurusrex
Copy link
Copy Markdown
Member Author

After discussion with @dingsdax, perhaps enforcing the commit message convention on each commit is overkill, as we typically squash and merge anyways.

We plan to introduce a new PR template, which would instruct contributors to follow the commit naming convention in the PR title, let's see if that solves the problem before reconsidering automated enforcement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants