Conversation
- disable MULTI_STATUS so no GITHUB_TOKEN is required (v7 aborts otherwise) - restrict to yamllint via VALIDATE_YAML - fix FILTER_REGEX_INCLUDE, which matched no files since the repo layout changed - fetch full history as recommended by super-linter Signed-off-by: DoDiODev <DoDiDev@proton.me>
DoDiODev
force-pushed
the
ci/super-linter-v7
branch
from
September 29, 2026 10:50
d01bbc1 to
df13bab
Compare
Contributor
Author
|
Verification run from my fork (throwaway PR DoDiODev#59, same commit, base = upstream/main b0a7589): https://github.com/DoDiODev/devlake/actions/runs/36562234835
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Supersedes #9104 (Dependabot: bump
github/super-linterfrom 4 to 7) and makes theyaml-lintworkflow pass with v7.Why #9104 fails
super-linter v7 aborts when commit status reports are enabled (
MULTI_STATUS, defaulttrue) and noGITHUB_TOKENis provided:v4 only logged this as an error and continued.
Pre-existing issue found along the way
FILTER_REGEX_INCLUDE: workspace/(docker-compose.yml|deployment/k8s/k8s-deploy.yaml)matches no file anymore: there is no rootdocker-compose.yml, and the k8s manifest lives indevops/deployment/k8s/. The current v4 job onmaintherefore lints nothing ("The script has completed" without any linter run).Changes to
.github/workflows/yaml-lint.ymlgithub/super-linter/slim@v4→@v7MULTI_STATUS: false: no token orstatuses: writepermission needed, and it also works for PRs from forksVALIDATE_YAML: true: only yamllint runs. Otherwise v7 would also run kubeconform, checkov, etc. on the k8s manifest.FILTER_REGEX_INCLUDE, which now matchesdevops/deployment/k8s/k8s-deploy.yaml,docker-compose-dev-mysql.yml,docker-compose-dev-postgresql.ymlanddocker-compose.datasources.yml(works for both relative and absolute paths)fetch-depth: 0on checkout, as recommended by super-linterVerified locally with yamllint 1.x and the super-linter v7 default
.yaml-lint.yml: warnings only (document-start, line-length), no errors.Does this close any open issues?
Supersedes #9104
Other Information
github/super-linteris a GitHub-maintained fork; upstreamsuper-linter/super-linteris at v8, but would need to be added to the ASF actions allowlist first. Staying on thegithub/*namespace avoids that.