chore: Add commit message linter

Author: cmfcmf

.github/workflows/commitlint.yml

@@ -0,0 +1,11 @@
+name: Lint Commit Messages
+on: [pull_request]
+
+jobs:
+  commitlint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+      - uses: wagoid/commitlint-github-action@v5

.husky/commit-msg

@@ -0,0 +1,6 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+if git-branch-is main; then
+  npx --no -- commitlint --edit
+fi

CONTRIBUTING.md

@@ -15,3 +15,31 @@ To get up and running, follow these steps:
 6. Test search manually: `npm run serve`
 
 You can view debug information at http://localhost:3000/\_\_docusaurus/debug (generated by [@docusaurus/plugin-debug](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-debug))
+
+## Commit Message Guidelines
+
+Commit messages for this repository should follow the "Conventional Commits" specification.
+Each message must start with one of the following keywords:
+
+```
+build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test
+```
+
+Include a brief description after the keyword, starting with a capital letter and no ending period. For example:
+
+```
+fix: Add German translation
+feat: Add better search integration
+chore: Update dependencies
+docs: Added more detailed documentation
+```
+
+Please use `feat` for new features, `fix` for bug fixes, or one of the other keywords when appropriate.
+
+To mark breaking changes, include a `!` after the keyword. For example:
+
+```
+chore!: Require Node.js v16
+```
+
+By following these guidelines, we can ensure that our commit messages are clear and consistent, which makes it easier to automatically generate changelogs.

commitlint.config.js

@@ -0,0 +1,8 @@
+module.exports = {
+  extends: ["@commitlint/config-conventional"],
+  rules: {
+    "subject-case": [2, "always", "sentence-case"],
+  },
+  helpUrl:
+    "https://github.com/cmfcmf/docusaurus-search-local/blob/main/CONTRIBUTING.md#commit-message-guidelines",
+};