[MegaLinter] Apply linters fixes

Author: renovate[bot]

.automation/build.py

@@ -11,10 +11,10 @@
 import subprocess
 import sys
 from datetime import date, datetime
+from pathlib import Path
 from shutil import copyfile, which
 from typing import Any
 from urllib import parse as parse_urllib
-from pathlib import Path
 
 import git
 import jsonschema
@@ -831,7 +831,9 @@ def generate_linter_dockerfiles():
         logging.info(f"Updated {linters_matrix_file}")
 
     # Write MD file
-    Path(f"{REPO_HOME}/docs/standalone-linters.md").write_text(linters_md + "\n", encoding="utf-8")
+    Path(f"{REPO_HOME}/docs/standalone-linters.md").write_text(
+        linters_md + "\n", encoding="utf-8"
+    )
 
 
 # Automatically generate a test class for each linter class

docs/descriptors/repository_gitleaks.md

@@ -34,18 +34,18 @@ If MegaLinter with gitleaks runs against a PR on a platform not listed above, an
 
 You can still choose to scan only PR commits in your CI/CD platform by setting the following MegaLinter environment variables:
 
-  - `PULL_REQUEST=true`\*
-  - `REPOSITORY_GITLEAKS_PR_COMMITS_SCAN: true`
-  - `REPOSITORY_GITLEAKS_PR_SOURCE_SHA` with last commit sha from your PR and `REPOSITORY_GITLEAKS_PR_TARGET_SHA` commit sha from your target branch (for example, `main` if you do PR to main branch)
+- `PULL_REQUEST=true`\*
+- `REPOSITORY_GITLEAKS_PR_COMMITS_SCAN: true`
+- `REPOSITORY_GITLEAKS_PR_SOURCE_SHA` with last commit sha from your PR and `REPOSITORY_GITLEAKS_PR_TARGET_SHA` commit sha from your target branch (for example, `main` if you do PR to main branch)
 
     Example commands:
 
-      - Source commit SHA:
+  - Source commit SHA:
         ```bash
         git rev-list -n 1 refs/remotes/origin/<source_branch>
         ```
 
-      - Target commit SHA:
+  - Target commit SHA:
         ```bash
         git rev-parse refs/remotes/origin/<target_branch>
         ```