docs: note PR titles must follow conventional commits - #169
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
marcossevilla
approved these changes
Sep 30, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Documents that PR titles must follow Conventional Commits.
Why
PRs are squash-merged with the PR title as the commit message, and release-please builds the changelog from those titles. A non-conventional PR title silently breaks release notes. The rule was only implied by the commit convention section.
Changes
CONTRIBUTING.md: note under Commit Convention explaining squash-merge + release-please, and a Pull Requests bullet requiring a Conventional Commits PR titleMirrors VeryGoodOpenSource/vgv-ffca-plugin#13.
🤖 Generated with Claude Code