Skip to content
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

prepare CRAN submission #592

Merged
merged 3 commits into from
Jun 2, 2023
Merged

prepare CRAN submission #592

merged 3 commits into from
Jun 2, 2023

Conversation

strengejacke
Copy link
Member

No description provided.

@codecov-commenter
Copy link

codecov-commenter commented Jun 2, 2023

Codecov Report

Merging #592 (64e5c73) into main (c315c97) will increase coverage by 0.05%.
The diff coverage is 100.00%.

❗ Current head 64e5c73 differs from pull request most recent head df6dba9. Consider uploading reports for the commit df6dba9 to get more accurate results

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@            Coverage Diff             @@
##             main     #592      +/-   ##
==========================================
+ Coverage   51.21%   51.26%   +0.05%     
==========================================
  Files          84       84              
  Lines        5762     5768       +6     
==========================================
+ Hits         2951     2957       +6     
  Misses       2811     2811              
Impacted Files Coverage Δ
R/check_model.R 31.29% <100.00%> (+1.43%) ⬆️
R/check_predictions.R 25.33% <100.00%> (+1.52%) ⬆️

@strengejacke
Copy link
Member Author

@IndrajeetPatil I'm planning to submit performance to CRAN the next days. It would be great if see could be submitted next, after performance. Do you have time to prepare a CRAN submission like end of next week or the next week after next?

@etiennebacher Would you like to finish your work on easystats/see#293 before submitting an update of see to CRAN?

@IndrajeetPatil
Copy link
Member

@IndrajeetPatil I'm planning to submit performance to CRAN the next days. It would be great if see could be submitted next, after performance. Do you have time to prepare a CRAN submission like end of next week or the next week after next?

Sure, I can do this next week.

@etiennebacher
Copy link
Member

@etiennebacher Would you like to finish your work on easystats/see#293 before submitting an update of see to CRAN?

Yes I'll try to finish this in the next few days

@strengejacke strengejacke merged commit b382504 into main Jun 2, 2023
@strengejacke strengejacke deleted the rc_0_10_4 branch June 2, 2023 11:42
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.

4 participants