From ff841c05206348c795d4541a7bd19a10c923f396 Mon Sep 17 00:00:00 2001 From: xibz <impactbchang@gmail.com> Date: Tue, 14 May 2024 13:46:23 -0500 Subject: [PATCH] Consistent strings in yaml Signed-off-by: xibz <impactbchang@gmail.com> --- .github/linters/.eslintrc.yml | 5 +---- .github/workflows/main.yml | 12 +++++++++++- 2 files changed, 12 insertions(+), 5 deletions(-) diff --git a/.github/linters/.eslintrc.yml b/.github/linters/.eslintrc.yml index 360a642c..73cf50e6 100644 --- a/.github/linters/.eslintrc.yml +++ b/.github/linters/.eslintrc.yml @@ -1,10 +1,7 @@ plugins: - jsonc overrides: - - files: - - "schemas/*.json" - - "examples/*.json" - parser: "jsonc-eslint-parser" + - parser: jsonc-eslint-parser rules: # These are the set of rules that belong to jsonc. For more information, # https://ota-meshi.github.io/eslint-plugin-jsonc/rules diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index 41a971ec..affa29ee 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -28,10 +28,20 @@ jobs: uses: github/super-linter/slim@v4 env: VALIDATE_ALL_CODEBASE: true - DEFAULT_BRANCH: main GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} VALIDATE_MARKDOWN: true VALIDATE_JSON: true + # superlinter runs each linter on a per file bases and does not look + # at tool specific configuration to determine whether or not to the + # lint the given file. + # + # Due to that we need to globally include or exclude files. This also + # makes tools less flexible with one another in that if a tool + # requires a specific folder to be included and excluded, but other + # tools require must lint the excluded folder, then this pattern does + # not work. Instead superlinter cannot be used in that case, and the + # linter itself needs to be ran outside of superlinter. + FILTER_REGEX_INCLUDE: .*\/(custom|examples|schemas)\/.* jsonschema: name: Validate Schemas and Examples