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

Update devel with Admiral v0.11.1 (#1997) patch #1998

Closed
wants to merge 1 commit into from
Closed

Update devel with Admiral v0.11.1 (#1997) patch #1998

wants to merge 1 commit into from

Conversation

bms63
Copy link
Collaborator

@bms63 bms63 commented Jul 5, 2023

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.

Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

  • Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
  • Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
  • Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
  • If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
  • Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
  • Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
  • Address any updates needed for vignettes and/or templates
  • Update NEWS.md if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
  • Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
  • Address or fix all lintr warnings and errors - lintr::lint_package()
  • Run R CMD check locally and address all errors and warnings - devtools::check()
  • Link the issue in the Development Section on the right hand side.
  • Address all merge conflicts and resolve appropriately
  • Pat yourself on the back for a job well done! Much love to your accomplishment!

* [actions skip] Add/Update README.md for patch

* Closes #1962 #1969 admiral 0.11.1 hotfix for get started link, derive_param_tte, derive_vars_joined (#1987)

* feat #1962 #1969 param_tte and get started fix

* forgot to add updated DESCRIPTION

* chore: #1962 thought crossing was dplyr

* chore: #1962 account for new assertions

* fix: #1962 was missing the reassignment piece?

* fix: #1966 crude answer

* feat: #1966 potential way of warning users of null new_vars

* fix: #1966 add appropriate assertions to get check to go through

* fix: #1966 appropriate function fix for order

* fix: #1966 vignette named order expression

* chore: #1966 try something

* chore: #1966 optionality of expressions is tricky

* feat: #1966 undo derive_joined stuff

* chore: run styler

---------

Co-authored-by: Zelos Zhu <zdz2101@github.com>

---------

Co-authored-by: Ben Straub <ben.x.straub@gsk.com>
Co-authored-by: GitHub Actions <action@github.com>
Co-authored-by: Zelos Zhu <zdz2101@github.com>
@bms63 bms63 requested review from zdz2101 and bundfussr July 5, 2023 17:48
Copy link
Collaborator

@zdz2101 zdz2101 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might need to use a copy of main branch to resolve conflicts then merge to devel?

@bms63 bms63 closed this Jul 5, 2023
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.

2 participants