Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

pyrefly report -> pyrefly coverage report#3340

Open
jorenham wants to merge 2 commits intofacebook:mainfacebook/pyrefly:mainfrom
jorenham:report->coverage_reportjorenham/pyrefly:report->coverage_reportCopy head branch name to clipboard
Open

pyrefly report -> pyrefly coverage report#3340
jorenham wants to merge 2 commits intofacebook:mainfacebook/pyrefly:mainfrom
jorenham:report->coverage_reportjorenham/pyrefly:report->coverage_reportCopy head branch name to clipboard

Conversation

@jorenham
Copy link
Copy Markdown
Contributor

@jorenham jorenham commented May 8, 2026

Summary

This renames the pyrefly report command to pyrefly coverage report. It's more specific this way, and makes is possible to add other commands related to type-coverage in the future (for example pyrefly coverage check to check that the coverage is above a given %).

The pyrefly report command still exists as a deprecated alias to pyrefly coverage report for the sake of backwards compatibility.

Test Plan

Added scrut CLI tests.

@meta-cla meta-cla Bot added the cla signed label May 8, 2026
@github-actions github-actions Bot added the size/s label May 8, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 8, 2026

According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅

@yangdanny97
Copy link
Copy Markdown
Contributor

@maggiemoss

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.