Skip to content

Conversation

@kelly-sovacool
Copy link
Member

Changes

Issues

#114

PR Checklist

(Strikethrough any points that are not applicable.)

  • This comment contains a description of changes with justifications, with any relevant issues linked.
  • Write unit tests for any new features, bug fixes, or other code changes.
  • Update the docs if there are any API changes (roxygen2 comments, vignettes, readme, etc.).
  • Update NEWS.md with a short description of any user-facing changes and reference the PR number. Follow the style described in https://style.tidyverse.org/news.html
  • Run devtools::check() locally and fix all notes, warnings, and errors.

@kopardev kopardev added the MOSuite RepoName label Jul 29, 2025
@codecov
Copy link

codecov bot commented Aug 22, 2025

Codecov Report

❌ Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 72.11%. Comparing base (dd90d04) to head (e836883).

Files with missing lines Patch % Lines
R/render_report.R 0.00% 5 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #120      +/-   ##
==========================================
- Coverage   72.31%   72.11%   -0.20%     
==========================================
  Files          19       20       +1     
  Lines        1842     1847       +5     
==========================================
  Hits         1332     1332              
- Misses        510      515       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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

Labels

MOSuite RepoName

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants