Is your feature request related to a problem? Please describe.
respect logs in CI can be very large and noisy, which increases storage usage and makes results harder to read.
Current formats:
lint: stylish, codeframe, json, checkstyle, codeclimate, summary, markdown, github-actionsscorecard-classic: stylish, jsonstats: stylish, json, markdown
Describe the solution you'd like
-
Add formats to respect commands (e.g. codeclimate, github-actions, summary...)
-
Add additional CI-friendly format:
- Optional: if
--format is not provided, detect CI and pick a better default format.
Describe alternatives you've considered
Additional context
Formats in oxlint: https://oxc.rs/docs/guide/usage/linter/output-formats
Vitest reporters: https://vitest.dev/guide/reporters.html#built-in-reporters
Is your feature request related to a problem? Please describe.
respectlogs in CI can be very large and noisy, which increases storage usage and makes results harder to read.Current formats:
lint:stylish,codeframe,json,checkstyle,codeclimate,summary,markdown,github-actionsscorecard-classic:stylish,jsonstats:stylish,json,markdownDescribe the solution you'd like
Add formats to
respectcommands (e.g.codeclimate,github-actions,summary...)Add additional CI-friendly format:
junit(JUnit XML) for CI test reports (GitLab / Bitbucket)https://docs.gitlab.com/ci/testing/unit_test_reports/#junit-xml-format-specification
https://support.atlassian.com/bitbucket-cloud/docs/test-reporting-in-pipelines/
--formatis not provided, detect CI and pick a better default format.Describe alternatives you've considered
Additional context
Formats in oxlint: https://oxc.rs/docs/guide/usage/linter/output-formats
Vitest reporters: https://vitest.dev/guide/reporters.html#built-in-reporters