Merge pull request #5 from DimitriPapadopoulos/node20

chore: run on node 20

.pre-commit-config.yaml

@@ -0,0 +1,29 @@
+---
+repos:
+  - repo: https://github.com/executablebooks/mdformat
+    # Do this before other tools "fixing" the line endings
+    rev: 0.7.17
+    hooks:
+      - id: mdformat
+        name: Format Markdown
+        entry: mdformat # Executable to run, with fixed options
+        language: python
+        types: [markdown]
+        args: [--wrap, "75", --number]
+        additional_dependencies:
+          - mdformat-toc
+          - mdformat-beautysh
+          # -mdformat-shfmt
+          # -mdformat-tables
+          - mdformat-config
+          - mdformat-black
+          - mdformat-web
+          - mdformat-gfm
+  - repo: https://github.com/adrienverge/yamllint.git
+    rev: v1.33.0
+    hooks:
+      - id: yamllint
+        args:
+          - --no-warnings
+          - -d
+          - "{extends: relaxed, rules: {line-length: {max: 90}}}"

README.md

@@ -3,7 +3,8 @@
 This problem matcher lets you show errors from GNU `sort` as annotation in
 GitHub Actions.
 
-Based on [korelstar](https://github.com/korelstar)'s [xmllint-problem-matcher](https://github.com/korelstar/xmllint-problem-matcher).
+Based on [korelstar](https://github.com/korelstar)'s
+[xmllint-problem-matcher](https://github.com/korelstar/xmllint-problem-matcher).
 
 ## Inputs
 
@@ -18,5 +19,5 @@ No outputs are generated apart from a configured problem matcher.
 Add the step to your workflow, before `sort -c` is called.
 
 ```yaml
-    - uses: codespell-project/sort-problem-matcher@v1
+  - uses: codespell-project/sort-problem-matcher@v1
 ```

action.yml

@@ -2,7 +2,7 @@ name: 'sort problem matcher'
 author: 'Peter Newman'
 description: 'Shows GNU sort errors as annotation (with file and code line) in GitHub Actions'
 runs:
-  using: 'node16'
+  using: 'node20'
   main: 'index.js'
 branding:
   icon: 'search'