-
Notifications
You must be signed in to change notification settings - Fork 174
carryforward flag switch #1126
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
base: master
Are you sure you want to change the base?
carryforward flag switch #1126
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1126 +/- ##
==========================================
- Coverage 87.85% 79.77% -8.08%
==========================================
Files 69 69
Lines 13515 13491 -24
==========================================
- Hits 11873 10763 -1110
- Misses 1642 2728 +1086
|
This did not work as I expected. I'll look into it! After a bit of research, it seems like I may have to add something like this: https://docs.codecov.com/docs/commit-status#flag_coverage_not_uploaded_behavior |
00430ee
to
4e74c2e
Compare
What is the status on this? |
Hi! This is on the back burner until I address #1077 is addressed. |
This turns the method filter flag to "true". This completes the carryforward initial implementation, ensuring coverage can remain accurate as we filter tests. Allows the methods tests to only run when a file in the methods folder has changed #1086 , but ensure the previous methods coverage report is carried forward and uploaded to codecov if it hasn't been regenerated for the current pull request ( #1101 and this pull request).