fix: extension tests for special usecase

.github/PULL_REQUEST/pull_request_template.md

@@ -30,5 +30,6 @@
 <!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
 <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
 
+- [ ] I have read CONTRIBUTING.md
 - [ ] I have updated the documentation accordingly.
 - [ ] I have added tests to cover my changes.

.husky/commit-msg

@@ -0,0 +1 @@
+npx --no -- commitlint --edit $1

.husky/pre-commit

@@ -0,0 +1,3 @@
+npm run lint
+npm run format
+npm test

.prettierignore

@@ -1,4 +1,11 @@
 # Ignore artifacts:
 out
 coverage
-node_modules
+node_modules
+.github
+.husky
+.vscode
+.vscode-test
+dist
+*.vsix
+

CONTRIBUTING.md

@@ -56,3 +56,13 @@ Our commit convention follow the [Conventional Commits 1.0.0-beta.4](https://www
 ### Sign commit message
 
 Please consider signing the commit message at least with `Signed-Off-By`. This is a way to certify that you wrote the code or otherwise have the right to pass it on as an open-source patch. The process is simple: if you can certify the [Developer's Certificate of Origin](https://developercertificate.org/) (DCO), then just add a line to every git commit message:
+
+### Commit hooks
+
+This repository uses [husky](https://typicode.github.io/husky/) for commit hooks.
+For each commit, the following checks are performed:
+
+- Lint
+- Format
+- Tests
+- Commit message convention check