docs: clarify commit message requirements in contribution.md (#1416)

google · Nov 28, 2024 · 4ba4a92 · 4ba4a92
1 parent 9e98057
commit 4ba4a92
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -106,7 +106,7 @@ To lint your code, run
 
 ### Making commits
 
-Please follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification for commit messages. This helps us to automate processes like changelog generation and ensures a clear and consistent commit history.
+Please follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification when squashing commits during a merge. This is typically the commit merged into the main branch and is often based on the PR title. Doing so helps us to automate processes like changelog generation and ensures a clear and consistent commit history.
 
 Some types: `feat:`, `fix:`, `docs:`, `chore:`, `refactor:`, and others.