Optimize super-linter to validate only Markdown files#8014
Merged
Conversation
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 super-linter job was taking 12m 51s because it ran all linters despite its documented purpose of validating only Markdown files. Other linters (Go, JavaScript, YAML, Shell) already run in separate CI jobs.
Changes
Configure super-linter environment variables:
VALIDATE_MARKDOWN: "true"- Enable Markdown validationVALIDATE_ALL_CODEBASE: "false"- Disable redundant lintersUpdate workflow description to reflect actual scope: "Markdown quality checks" instead of "comprehensive code quality checks"
Performance Impact
Expected runtime: ~1-2 minutes (down from 12m 51s)
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.