Continue-on-error fix --check, with ci alias and CI Markdown report - #374
Merged
Conversation
`fix --check` (and its shorter task alias `ci`) now runs every check even when an earlier one fails so a single CI run surfaces every formatter/linter violation at once. When the `CI` environment variable is set, a Markdown status table is written to `$GITHUB_STEP_SUMMARY` (or `target/fix-check-summary.md` if unset) so the report renders on the GitHub Actions workflow summary page.
github-actions
Bot
added
🚀 feature
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
1 participant
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.
🚀 What's included in this PR?
fix --checknow runs every check even when an earlier one fails, so a single CI run surfaces every formatter/linter violation at once. Exits non-zero if any failed.citask as a per-project shorthand forfix --check(my-project/ciworks too).CIenvironment variable is set, the run also prints a labelled banner per check, logs aPASS/FAILsummary, and writes a Markdown status table to$GITHUB_STEP_SUMMARY(ortarget/fix-check-summary.mdif unset). Local invocations stay quiet.NamedCheckwrapper forfixCheckExtraentries.someTask.named("my-linter")(viaNamedCheckOps) is the recommended form; the explicitNamedCheck("my-linter", someTask)also works.fixandcitasks no longer aggregate at the sbt-task level; multi-project coverage is achieved internally via a new.acrossAggregatedcombinator so a single invocation produces a single plan/summary block.versionPolicyIntention := Compatibility.Nonefor this release (breaking change:fixCheckExtra's element type becameNamedCheck).