Repository navigation
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.
fix: reduce Super Linter fixture noise and preserve failure diagnostics #68733
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: reduce Super Linter fixture noise and preserve failure diagnostics #68733
Changes from all commits
d17abb2File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
L60-74: delete: brittle source/lock text-presence mirror for unrelated reporting behavior. Keep the path-matching checks above; workflow compilation and drift checks cover generated lock consistency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This regression test is overfitted to prompt prose, so a harmless wording cleanup will start failing
make test-scriptsand block unrelated workflow changes.💡 Why this is risky and how to tighten it
Right now the assertions on
"twenty examples total"and"does not establish an exploitable vulnerability"are checking editorial phrasing rather than the scope/reporting behavior this test is supposed to protect. That makes the test noisy to maintain and encourages cargo-cult prompt wording instead of letting us revise instructions safely.A safer pattern is to keep the structural checks here (
FILTER_REGEX_EXCLUDE,continue-on-error, result artifact path, missing-log failure) and drop the exact English sentence matches, or replace them with a smaller semantic anchor that is unlikely to change during prompt edits.That still guards the workflow contract without turning copy edits into failing tests.
Uh oh!
There was an error while loading. Please reload this page.