-
Notifications
You must be signed in to change notification settings - Fork 63
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
Documentation: Bring cheatsheet into alignment with 1.1.0 changes #2458
Comments
I had a look. I think we don't need to update I would update only However, I noticed that the webpage links to the development version of the cheatsheet. I.e., the users already see the @bms63 , @manciniedoardo , what do you think? |
I like submitting to rstudio/cheatsheets. Gets us more exposure. |
I like the idea too! |
OK, I'll submit the cheatsheet for 1.1.1. |
@manciniedoardo , for the submission to rstudio/cheatsheets I need to add an author name to the cheatsheet. As you did most of the work, I would suggest to add your name. Do you agree? |
@bundfussr yes sure, thanks! |
I've submitted the cheatsheet: rstudio/cheatsheets#555 |
Thanks @bundfussr !! |
I've created the branch |
This issue is stale because it has been open for 90 days with no activity. |
Please select a category the issue is focused on?
User Guides
Let us know where something needs a refresh or put your idea here!
We need to align the cheatsheet to admiral 1.1.0. As far as I can tell only
derive_var_trtemfl()
needs a slight update for new argument. However, there could be others!Current Cheat Sheet
https://github.com/pharmaverse/admiral/blob/main/inst/cheatsheet/admiral_cheatsheet.pdf
Use this powerpoint to modify Cheat Sheet
https://github.com/pharmaverse/admiral/blob/main/inst/cheatsheet/admiral_cheatsheet.pptx
Definition of Done
@pharmaverse/admiral @pharmaverse/admiral_comm Great way to get more familiar with the package. I would imagine this is a 1-2 hour task. This does not impact 1.1.0 release timelines and so is not needed immediately...but nice to have in the next week.
The text was updated successfully, but these errors were encountered: