chore: fix lint issues

Signed-off-by: Emilien Escalle <emilien.escalle@escemi.com>

Author: neilime

.github/linters/.jscpd.json

@@ -1,4 +1,4 @@
 {
   "threshold": 5,
-  "ignore": ["/workspace/actions/**/README.md"]
+  "ignore": ["**/tests/*"]
 }

.github/linters/.yaml-lint.yml

@@ -2,7 +2,7 @@
 extends: default
 
 ignore:
-  - /github/workspace/tests/charts/
+  - "**/tests/charts/**"
 
 rules:
   line-length:

.github/workflows/docker-build-images.md

@@ -235,6 +235,10 @@ If a platform entry omits the <code>runs-on</code> field, the following default
 - When the main <code>docker-build-images</code> job uses a standard hosted runner, that runner is automatically matched to each platform.
 - If the main <code>docker-build-images</code> job uses a custom or self-hosted runner, all platforms use the same runner.
 
+<!--
+// jscpd:ignore-start
+-->
+
 <!-- outputs:start -->
 
 ## Outputs
@@ -252,10 +256,6 @@ If a platform entry omits the <code>runs-on</code> field, the following default
 <!-- examples:start -->
 <!-- examples:end -->
 
-<!--
-// jscpd:ignore-start
--->
-
 <!-- contributing:start -->
 
 ## Contributing

README.md

@@ -76,13 +76,36 @@ actions/{category}/{action-name}/
 1. **Consistent branding**: Use `author: hoverkraft` with `color: blue` and a meaningful `icon`.
 2. **Pinned dependencies**: Reference third-party actions via exact SHAs to guarantee reproducibility.
 3. **Input validation**: Validate critical inputs early within composite steps or supporting scripts.
+4. **Idempotent steps**: Ensure actions can run multiple times without leaving residual state in the workspace.
+5. **Multi-platform support**: Test actions in both `ubuntu-latest` and `windows-latest` runners when applicable.
+6. **Cross-platform compatibility**: Uses `actions/github-script` steps for cross-platform compatibility. Avoid `run` steps.
+7. **Logging**: Use structured logs with clear prefixes (`[build-image]`, `[helm-test-chart]`, …) to simplify debugging.
+8. **Security**: Avoid shell interpolation with untrusted inputs; prefer parameterized commands or `set -euo pipefail` wrappers.
+
+#### File Conventions
+
+- **Dockerfile**: Provides the Super Linter environment with UID/GID passthrough for local dev parity.
+- **Tests**: Located in `tests/` with fixtures for container builds and chart-testing scenarios.
+- **Workflows**: Reusable definitions live in `.github/workflows/`; internal/private workflows are prefixed with `__`.
+
+#### JavaScript Development Patterns
+
+- Encapsulate reusable logic in modules under the action directory (for example, `actions/my-action/index.js`).
+- Prefer async/await with explicit error handling when interacting with the GitHub API or filesystem.
+- Centralize environment variable parsing and validation to keep composite YAML lean.
 
 #### Container Delivery Patterns
 
 - Prefer multi-architecture builds via `docker buildx build` with explicit `--platform` lists.
 - Surface provenance metadata through outputs (`image-name`, `digest`, etc.) to unblock downstream jobs.
 - Keep secrets and registry credentials in GitHub environments or organization secrets—never hardcode them.
 
+#### Helm Testing Patterns
+
+- Use the chart fixtures under `tests/charts/` to exercise Helm-focused actions.
+- Maintain `Chart.lock` files alongside `Chart.yaml` to document dependency revisions.
+- Commit `ci/empty-values.yaml` templates for creating scenario-specific overrides.
+
 ### Development Workflow
 
 #### Linting & Testing
@@ -96,30 +119,6 @@ make test-build-application  # Build and push the sample test application image
 make test-ct-install         # Validate Helm charts via chart-testing
 ```
 
-#### File Conventions
-
-- **Dockerfile**: Provides the Super Linter environment with UID/GID passthrough for local dev parity.
-- **Tests**: Located in `tests/` with fixtures for container builds and chart-testing scenarios.
-- **Workflows**: Reusable definitions live in `.github/workflows/`; internal/private workflows are prefixed with `__`.
-
-#### Action Development Conventions
-
-1. **Idempotent steps**: Ensure actions can run multiple times without leaving residual state in the workspace.
-2. **Logging**: Use structured logs with clear prefixes (`[build-image]`, `[helm-test-chart]`, …) to simplify debugging.
-3. **Security**: Avoid shell interpolation with untrusted inputs; prefer parameterized commands or `set -euo pipefail` wrappers.
-
-#### JavaScript Development Patterns
-
-- Encapsulate reusable logic in modules under the action directory (for example, `actions/docker/prune-pull-requests-image-tags/index.js`).
-- Prefer async/await with explicit error handling when interacting with the GitHub API or filesystem.
-- Centralize environment variable parsing and validation to keep composite YAML lean.
-
-#### Helm Testing Patterns
-
-- Use the chart fixtures under `tests/charts/` to exercise Helm-focused actions.
-- Maintain `Chart.lock` files alongside `Chart.yaml` to document dependency revisions.
-- Commit `ci/empty-values.yaml` templates for creating scenario-specific overrides.
-
 ## Author
 
 🏢 **Hoverkraft <contact@hoverkraft.cloud>**

actions/docker/build-image/action.yml

@@ -242,6 +242,7 @@ runs:
       with:
         platforms: ${{ inputs.platform }}
 
+    # jscpd:ignore-start
     - uses: docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435 # v3.11.1
       with:
         # FIXME: upgrade version when available (https://github.com/docker/buildx/releases)
@@ -255,6 +256,7 @@ runs:
         registry: ${{ inputs.oci-registry }}
         username: ${{ inputs.oci-registry-username }}
         password: ${{ inputs.oci-registry-password }}
+    # jscpd:ignore-end
 
     - id: build
       uses: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83 # v6.18.0

tests/charts/application/README.md

@@ -6,9 +6,9 @@ A Helm chart for Kubernetes
 
 ## Requirements
 
-| Repository                         | Name  | Version |
-| ---------------------------------- | ----- | ------- |
-| https://charts.bitnami.com/bitnami | mysql | 14.0.3  |
+| Repository                           | Name  | Version |
+| ------------------------------------ | ----- | ------- |
+| <https://charts.bitnami.com/bitnami> | MySQL | 14.0.3  |
 
 ## Values
 

tests/charts/umbrella-application/README.md

@@ -6,10 +6,10 @@ An umbrella Helm chart for Kubernetes
 
 ## Requirements
 
-| Repository                         | Name            | Version |
-| ---------------------------------- | --------------- | ------- |
-| file://./charts/app                | app             | 0.0.0   |
-| https://charts.bitnami.com/bitnami | database(mysql) | 14.0.3  |
+| Repository                           | Name            | Version |
+| ------------------------------------ | --------------- | ------- |
+| file://./charts/app                  | app             | 0.0.0   |
+| <https://charts.bitnami.com/bitnami> | database(MySQL) | 14.0.3  |
 
 ## Values