prettier

.github/workflows/lint.yml

@@ -22,3 +22,11 @@ jobs:
         uses: golangci/golangci-lint-action@v3
         with:
           version: v1.51.1
+
+      - name: prettier
+        uses: creyD/prettier_action@v4.3
+        with:
+          dry: True
+          file_pattern: '**/*.{js,md,yaml,yml,json}'
+          prettier_options: --check --config .prettierrc.yml .
+          github_token: ${{secrets.GH_PAT}}

.prettierignore

@@ -1 +1,3 @@
 docs/docs/changelog.md
+testdata
+docs/i18n

docs/babel.config.js

@@ -1,3 +1,3 @@
 module.exports = {
-  presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
+  presets: [require.resolve('@docusaurus/core/lib/babel/preset')]
 };

docs/docs/faq.md

@@ -14,8 +14,7 @@ current shell, so it can't change the environment of the shell that started it.
 This limitation is shared by other task runners and build tools too.
 
 A common way to work around this is to create a task that will generate output
-that can be parsed by your shell. For example, to set an environment variable on
-your shell you can write a task like this:
+that can be parsed by your shell. For example, to set an environment variable on your shell you can write a task like this:
 
 ```yaml
 my-shell-env: