Add non-blocking ty and pyrefly type checks to CI - #4401
Draft
garth-wells wants to merge 2 commits into
Draft
Conversation
Runs alongside the existing mypy checks in the lint job, with continue-on-error so failures are visible without blocking the pipeline. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Member
|
Typing fixes for pyrefly can be found on jhale/pyrefly, feel free to merge onto here. |
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
2 participants
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.
Summary
tyandpyreflyas additional Python type checkers in thelintjob ofccpp.yml, run alongside the existingmypychecks.continue-on-error: trueso they report diagnostics without blocking the pipeline.Test plan
ty checksandpyrefly checkssteps run in thelintjob on this PR and show as non-blocking (yellow/warning) even with diagnostics present.lintjob (ruff, clang-format, gersemi, mypy) is unaffected.