docs: Update commit message guidelines for clarity and consistency ✂️

0GiS0 · Dec 30, 2024 · 93e5d17 · 93e5d17
1 parent ac1e804
commit 93e5d17
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/copilot/commit-style.md b/docs/copilot/commit-style.md
@@ -1,2 +1,2 @@
 ## Commit messages
-If the commit is for a new feature should start with `feat: `, if it's for fixing a bug should start with `fix: `, if it's for performance improvements should start with `perf: `, if its for style or layout changes should start with `style: `, for minimum changes with no significant impact `chore: ` and for documentation `docs: `. Commits that don't fit in any of these categories should start with `refactor: `. Commit should be concise and clear, and should not exceed 100 characters. If the commit is related to an issue, the issue number should be included in the commit message.
+If the commit is for a new feature should start with `feat: `, if it's for fixing a bug should start with `fix: `, if it's for performance improvements should start with `perf: `, if its for style or layout changes should start with `style: `, for minimum changes with no significant impact `chore: ` and for documentation `docs: `. Commits that don't fit in any of these categories should start with `refactor: `. Commit should be concise and clear, and should not exceed 100 characters.