Exclude workflow YAML from MegaLinter lychee URL checks - #3864
#3864Exclude workflow YAML from MegaLinter lychee URL checks#3864plengauer with Copilot wants to merge 2 commits intomainplengauer/Thoth:mainfrom copilot/plengauer-lychee-flag-false-positiveplengauer/Thoth:copilot/plengauer-lychee-flag-false-positiveCopy head branch name to clipboard
Conversation
|
Hello, thanks for contributing for the first time! |
❌MegaLinter analysis: Error
Detailed Issues❌ REPOSITORY / devskim - 2027 errorsNo output available ❌ REPOSITORY / grype - 2 errorsNo output available ❌ COPYPASTE / jscpd - 70 errors❌ REPOSITORY / kingfisher - 1 errorNo output available ❌ REPOSITORY / osv-scanner - 2 errors❌ REPOSITORY / trivy - 11 errorsNo output available Notices📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining See detailed reports in MegaLinter artifacts
|
There was a problem hiding this comment.
Pull request overview
Note
Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.
Adds a MegaLinter configuration to stop Lychee (URL checking) from scanning GitHub Actions workflow files, reducing false-positive link failures from placeholders and runtime-only endpoints.
Changes:
- Introduced a repository-level
.mega-linter.ymlconfiguration file. - Configured Lychee to exclude
.github/workflows/from URL checks.

MegaLinter/lychee was reporting non-actionable link failures from hand-written workflow YAML where URLs are intentionally placeholders, expression fragments, or runtime-only endpoints. This change removes that false-positive class at the source by scoping lychee away from
.github/workflows/.Change
.mega-linter.yml..github/workflows/.Effect
x-access-tokenremote fragments, localhost OTLP endpoints used only during CI jobs).