chore(ci): full-scan MegaLinter on its own Renovate update PRs#81
Merged
Conversation
When Renovate bumps oxsecurity/megalinter, force VALIDATE_ALL_CODEBASE=true so the new version is exercised against the entire codebase before the PR merges. Other PRs and push-to-main keep their current default scan scope.
ChipWolf
force-pushed
the
wolf/hungry-almeida-a22f10
branch
from
d288048 to
abc1d92
Compare
2 tasks
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
oxsecurity/megalinter, setVALIDATE_ALL_CODEBASE=trueso the new MegaLinter version runs against every file, not just the workflow diff.github.event.pull_request.user.login == 'renovate[bot]'plusstartsWith(github.head_ref, 'renovate/oxsecurity-megalinter-'), which matches Renovate's existing branch-name convention for this action (e.g. PR #70'srenovate/oxsecurity-megalinter-9.x).trueonpush(matching MegaLinter's default on the default branch) andfalseon every other PR (matching the changed-files-only default).Why
A MegaLinter version bump can introduce new or stricter rules. Running it only over the workflow diff misses regressions hidden in unchanged files; a full repo scan on the upgrade PR surfaces them before merge so the auto-merge rule for minor/patch updates does not silently land a breaking version.
Test plan
oxsecurity/megalinterPR shows MegaLinter scanning the full repo (look forVALIDATE_ALL_CODEBASE: truein the action's startup log).mainafter merge runs a full scan as before.🤖 Generated with Claude Code