Bug was https://github.com/kucherenko/jscpd/issues/427, but was fixed in [email protected]
Details are in the linked issue, but essentially jspcd would fail to lint certain naughty strings.
super-linter just needs to update to the newest jscpd version to fix the issue.

@GaboFDC seems the bot is still acting up.
Jscpd should be up to date. Can you check? And specify what version and build of super linter are you using if you still the the issue?
Still seeing it on my repo, just ran this build. https://github.com/snowe2010/pretty-print/pull/56/checks?check_run_id=2072748513
Just using
name: Linter
# Run this workflow every time a new commit pushed to your repository
on: push
jobs:
lint:
name: Lint code base
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v2
- name: Run Super-Linter
uses: github/super-linter@v3
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
FILTER_REGEX_EXCLUDE: .*gradle/.*
VALIDATE_JAVA: false
VALIDATE_KOTLIN: false
VALIDATE_BASH: false
Seems like the issue is that v3 is pointing to v3.14.5
We will fix that, meanwhile, if you need a quick fix, you can point to latest, master, to specific 3.15.x
@GaboFDC @snowe2010 fixed and it shoudl be pulling latest version...
Seems GitHub had not accepted the terms of service for actions lol... and another small bug I'm hunting...
Hm. I'm still seeing those failures. I don't know how to tell if this is due to jspcd still having the bug, or if the correct version is not being used.
Please attach some debug logs to check
Most helpful comment