docs: Update commit message guidelines for clarity and conciseness 📜

0GiS0 · Dec 29, 2024 · f42dd1e · f42dd1e
1 parent 0b4edee
commit f42dd1e
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 2 deletions.
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
@@ -1,2 +1 @@
-## Commit messages
-The key to a good commit is clarity and conciseness. 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: `. The most important thing it to keep the messages clear and precise so that everyone working on the project can quickly understand the changes made.
+
diff --git a/.vscode/settings.json b/.vscode/settings.json
@@ -16,6 +16,9 @@
     },
     {
       "text": "Add emoji at the end of the message."
+    },
+    {
+      "file": "docs/code-style copy.md"
     }
   ],
   "github.copilot.chat.testGeneration.instructions": [

diff --git a/docs/code-style copy.md b/docs/code-style copy.md
@@ -0,0 +1,2 @@
+## Commit messages
+The key to a good commit is clarity and conciseness. 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: `. The most important thing it to keep the messages clear and precise so that everyone working on the project can quickly understand the changes made.
Original file line number	Diff line number	Diff line change
		@@ -1,2 +1 @@
		## Commit messages
		The key to a good commit is clarity and conciseness. 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: `. The most important thing it to keep the messages clear and precise so that everyone working on the project can quickly understand the changes made.
-Original file line number
+Diff line change
@@ Expand Up / @@ -16,6 +16,9 @@ @@
         },
         {
           "text": "Add emoji at the end of the message."
+        },
+        {
+          "file": "docs/code-style copy.md"
         }
       ],
       "github.copilot.chat.testGeneration.instructions": [
@@ Expand Down @@
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,2 @@
		## Commit messages
		The key to a good commit is clarity and conciseness. 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: `. The most important thing it to keep the messages clear and precise so that everyone working on the project can quickly understand the changes made.