Harden Super Linter workflow against generated-summary linting and log artifact permission failures#41729
Merged
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
Fix Super Linter markdown summary and log artifact failures
Harden Super Linter workflow against generated-summary linting and log artifact permission failures
Jun 26, 2026
Copilot created this pull request from a session on behalf of
pelikhan
June 26, 2026 15:10
View session
Contributor
There was a problem hiding this comment.
Pull request overview
This PR hardens the scheduled Super Linter Report workflow so it no longer self-lints generated output and so log artifact upload is more reliable across file ownership/permission boundaries. It updates both the markdown source workflow and the compiled lock workflow to keep runtime behavior aligned with the authored source.
Changes:
- Exclude generated
super-linter-output/artifacts from Markdown validation viaFILTER_REGEX_EXCLUDE. - Disable Super Linter’s step-summary env wiring in this workflow mode to avoid the summary formatting failure path.
- Improve log upload robustness by staging the log to
/tmp, emitting explicit warnings on failures, and making artifact upload non-fatal when missing.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/super-linter.md | Adds exclusion regex for generated output and stages the log to /tmp for permission-safe artifact upload. |
| .github/workflows/super-linter.lock.yml | Regenerates the compiled workflow to reflect the source workflow’s new env and log-upload behavior. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Low
pelikhan
approved these changes
Jun 26, 2026
Contributor
|
@copilot please post a short completion plan or the remaining blockers for the Super Linter workflow changes.
|
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
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.
The scheduled
Super Linter Reportworkflow was failing for two independent reasons: super-linter attempted to process its own generated summary output, and the post-step log artifact upload failed on file ownership/permission boundaries.Scope of fix
FILTER_REGEX_EXCLUDE.Log artifact reliability
super-linter.logwith a staged copy to/tmp/super-linter.log.if-no-files-found: ignore).Compiled workflow parity
.github/workflows/super-linter.lock.ymlfrom the markdown workflow so runtime behavior matches source.