Skip to content

🔧 - Update coverage config #28

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

Merged
merged 2 commits into from
Feb 6, 2022
Merged

🔧 - Update coverage config #28

merged 2 commits into from
Feb 6, 2022

Conversation

isac322
Copy link
Owner

@isac322 isac322 commented Feb 6, 2022

No description provided.

@isac322 isac322 self-assigned this Feb 6, 2022
@codecov
Copy link

codecov bot commented Feb 6, 2022

Codecov Report

Merging #28 (6395f57) into master (0d4c9d0) will not change coverage.
The diff coverage is n/a.

❗ Current head 6395f57 differs from pull request most recent head b802789. Consider uploading reports for the commit b802789 to get more accurate results

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #28   +/-   ##
=======================================
  Coverage   96.74%   96.74%           
=======================================
  Files           2        2           
  Lines         123      123           
=======================================
  Hits          119      119           
  Misses          4        4           
Flag Coverage Δ
3.1 95.12% <ø> (ø)
3.6 95.12% <ø> (ø)
3.7 95.12% <ø> (ø)
3.8 95.12% <ø> (ø)
3.9 95.12% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0d4c9d0...b802789. Read the comment docs.

@isac322 isac322 force-pushed the update_coverage_config branch from 6395f57 to b802789 Compare February 6, 2022 14:27
@isac322 isac322 merged commit 5970ca9 into master Feb 6, 2022
@isac322 isac322 deleted the update_coverage_config branch February 6, 2022 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant