-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a settings annotation to all new files #5313
base: main
Are you sure you want to change the base?
Conversation
QA Wolf here! As you write new code it's important that your test coverage is keeping up. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## jtran/fix-units-empty-program #5313 +/- ##
==============================================================
Coverage 86.05% 86.05%
==============================================================
Files 92 92
Lines 33284 33284
==============================================================
Hits 28643 28643
Misses 4641 4641
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
b3acb34
to
224c03f
Compare
Stacked on top of #5310. Another step towards #3960. Any new files now get a settings annotation based on the current setting value. Combined with #5212, this makes the project-level setting have no effect on newly-created files and projects, since inline annotations take precedence.