Repository navigation
chore(ci): enforce repository formatting in Check - #2022
Merged
Merged
Conversation
BlankParticle
changed the title
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.
Fail the Check workflow when repository formatting drifts by running the existing
pnpm format:check(oxfmt --check) after dependency installation. The command does not rewrite files, and its nonzero exit status fails the job.CI previously ran oxlint but never invoked the formatting check. The local pre-commit hook rewrites and restages formatting across the repository; it does not enforce formatting in CI. Remove workflow path filters so changes to any formatter-covered file or configuration trigger Check.
Apply the lockfile-pinned oxfmt 0.71.0 to all current drift: 10 QueueSink and WorkerProvider source/test files, including the QueueSink formatting removed from #1905. No behavior, dependency, or submodule-pin changes.