Better release notes, remove commit linting

.github/pr-labeler.yml

@@ -1,10 +1,11 @@
-feature: ['feature/*', 'feat/*']
+feature: ['feat/*']
 refactor: ['refactor/*']
-fix: ['fix/*', 'bugfix/*', 'hotfix/*']
+fix: ['fix/*']
 style: ['style/*']
 chore: ['chore/*']
 dependencies: ['deps/*', 'renovate/*']
 ci: ['ci/*']
 documentation: ['docs/*']
-tests: ['tests/*']
-optimization: ['optimization/*']
+tests: ['test/*']
+optimization: ['perf/*']
+revert: ['revert/*']

.github/release-drafter.yml

@@ -5,6 +5,9 @@ categories:
   - title: '🚀 Features'
     label: 'feature'
 
+  - title: '🔥 Revertions'
+    label: 'revert'
+
   - title: '🛠 Refactor'
     label: 'refactor'
 
@@ -27,23 +30,22 @@ categories:
     label: 'tests'
 
   - title: '🏎 Optimizations'
-    label: 'optimizations'
+    label: 'optimization'
 
 version-resolver:
   major:
     labels:
       - 'BREAKING CHANGES'
+      - 'revert'
   minor:
     labels:
       - 'feature'
-      - 'enhancement'
       - 'dependencies'
   patch:
     labels:
       - 'fix'
-      - 'bugfix'
       - 'bug'
-      - 'optimizations'
+      - 'optimization'
       - 'refactor'
       - 'style'
   default: patch

README.md

@@ -160,4 +160,4 @@ Then, the `release` workflow handles everything:
 
 - Should have human-readable name, for example: "Add a TODO list feature"
 - Should describe changes
-- Should have correct labels
+- Should have correct labels (handled by PR Labeler in most cases)