docs: improve and fix lint issues

Signed-off-by: Emilien Escalle <[email protected]>

Author: neilime

.github/workflows/continuous-integration.yml

@@ -55,7 +55,7 @@ on:
         description: |
           Whether to enable linting.
           Set to `null` or empty to disable.
-          Accepts a JSON object for lint options. See [lint action](../actions/lint/README.md).
+          Accepts a JSON object for lint options. See [lint action](../../actions/lint/README.md).
           It should generate lint reports in standard formats.
 
           Example: 
@@ -87,7 +87,7 @@ on:
         description: |
           Whether to enable testing.
           Set to `null` or empty to disable.
-          Accepts a JSON object for test options. See [test action](../actions/test/README.md).
+          Accepts a JSON object for test options. See [test action](../../actions/test/README.md).
           If coverage is enabled, it should generate test and coverage reports in standard formats.
 
           Example: 

actions/build/action.yml

@@ -15,19 +15,26 @@ inputs:
   build-commands:
     description: |
       List of build commands to execute, one per line.
-      These are npm/pnpm/Yarn script names (e.g., "build", "compile").
+      These are npm/pnpm/Yarn script names (e.g., `build`, `compile`).
     required: true
   build-env:
     description: |
       JSON object of environment variables to set during the build.
-      Example: {"NODE_ENV": "production", "API_URL": "https://api.example.com"}
+      Example:
+
+      ```json
+      {
+        "NODE_ENV": "production",
+        "API_URL": "https://api.example.com"
+      }
+      ```
     required: false
     default: "{}"
   build-secrets:
     description: |
-      Multi-line string of secrets in env format (KEY=VALUE).
+      Multi-line string of secrets in env format (`KEY=VALUE`).
       Example:
-      ```
+      ```txt
       SECRET_KEY=$\{{ secrets.SECRET_KEY }}
       API_TOKEN=$\{{ secrets.API_TOKEN }}
       ```
@@ -36,7 +43,14 @@ inputs:
   build-artifact:
     description: |
       JSON object specifying artifact upload configuration.
-      Format: {"name": "artifact-name", "paths": "path1\npath2"}
+      Example:
+
+      ```json
+      {
+        "name": "artifact-name",
+        "paths": "path1\npath2"
+      }
+      ```
     required: false
     default: ""
   container:

actions/lint/action.yml

@@ -18,16 +18,16 @@ inputs:
     default: "false"
   command:
     description: |
-      NPM/package manager script command to run for linting.
-      This should be a script defined in your package.json.
+      npm/pnpm/Yarn script command to run for linting.
+      This should be a script defined in your `package.json`.
       The command should generate lint report files in a standard format.
     required: false
     default: "lint:ci"
   report-file:
     description: |
       Optional lint report path forwarded to the [parse-ci-reports](https://hoverkraft-tech/ci-github-common/actions/parse-ci-reports) action.
       Provide an absolute path or one relative to the working directory.
-      When omitted, the action falls back to "auto:lint" detection.
+      When omitted, the action falls back to `auto:lint` detection.
     required: false
     default: ""
   path-mapping:

actions/test/action.yml

@@ -18,8 +18,8 @@ inputs:
     default: "false"
   command:
     description: |
-      NPM/package manager script command to run for testing.
-      This should be a script defined in your package.json.
+      npm/pnpm/Yarn script command to run for testing.
+      This should be a script defined in your `package.json`.
       The command should generate coverage report files in a standard format (Cobertura XML, lcov, etc.).
     required: false
     default: "test:ci"
@@ -33,11 +33,11 @@ inputs:
     default: "github"
   report-file:
     description: |
-      Optional test and coverage report paths forwarded to the hoverkraft-tech/ci-github-common/actions/parse-ci-reports action.
+      Optional test and coverage report paths forwarded to the [parse-ci-reports](https://hoverkraft-tech/ci-github-common/actions/parse-ci-reports) action.
       Supports multiple formats (Cobertura, OpenCover, lcov, etc.).
       Provide absolute paths or paths relative to the working directory.
       Multiple entries can be separated by newlines, commas, or semicolons.
-      When omitted, the action falls back to "auto:test,auto:coverage" detection.
+      When omitted, the action falls back to `auto:test,auto:coverage` detection.
     required: false
     default: ""
   path-mapping: