-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feature/14 review shiny ci cd #27
Conversation
…that travis ci isn't fully open source anymore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor reqording. My main request is to clarify better some steps in the yml files by adding some comments.
Co-authored-by: Francesca Vitalini <francesca.vitalini@mirai-solutions.com>
Co-authored-by: Francesca Vitalini <francesca.vitalini@mirai-solutions.com>
Co-authored-by: Francesca Vitalini <francesca.vitalini@mirai-solutions.com>
Co-authored-by: Francesca Vitalini <francesca.vitalini@mirai-solutions.com>
Co-authored-by: Francesca Vitalini <francesca.vitalini@mirai-solutions.com>
Co-authored-by: Francesca Vitalini <francesca.vitalini@mirai-solutions.com>
Co-authored-by: Francesca Vitalini <francesca.vitalini@mirai-solutions.com>
Co-authored-by: Francesca Vitalini <francesca.vitalini@mirai-solutions.com>
Thanks for the feedback @fvitalini , integrated most of it apart from the comments regarding the .yml files. As I mentioned already in miraisolutions/ShinyCICD#1, we need to decide on how much we want to comment these files to explain them better. @riccardoporreca Please let me know your opinion on this as well, and you can also review the changes now as I integrated Francesca's feedback. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See some refinements following the main restructuring with Actions are being the prominent part here. The main gap is talking about renv in the actions section.
Co-authored-by: Riccardo Porreca <riccardo.porreca@mirai-solutions.com>
Co-authored-by: Riccardo Porreca <riccardo.porreca@mirai-solutions.com>
Co-authored-by: Riccardo Porreca <riccardo.porreca@mirai-solutions.com>
Co-authored-by: Riccardo Porreca <riccardo.porreca@mirai-solutions.com>
Co-authored-by: Riccardo Porreca <riccardo.porreca@mirai-solutions.com>
Co-authored-by: Riccardo Porreca <riccardo.porreca@mirai-solutions.com>
Co-authored-by: Riccardo Porreca <riccardo.porreca@mirai-solutions.com>
Co-authored-by: Riccardo Porreca <riccardo.porreca@mirai-solutions.com>
Co-authored-by: Riccardo Porreca <riccardo.porreca@mirai-solutions.com>
Co-authored-by: Riccardo Porreca <riccardo.porreca@mirai-solutions.com>
Co-authored-by: Riccardo Porreca <riccardo.porreca@mirai-solutions.com>
…eem problematic in bookdown documents)
* In particular, mention the continuous deployment from `master` only, as in the Travis CI section.
* For the 4 flavors, using the `<details>` HTML tag providing implementing collapsible details.
* Missing in comparison to the Travis CI part, used as a starting point. * No specific details are included, just pointers to the renv vignette and the complete workflow files.
* Also fix the actual file content shown for each flavor
* Also including a comment
@Chargothrond, see my follow-up updates and other smaller refinements I committed. We may want to make sure there is full alignment with the workflows as showcased in miraisolutions/ShinyCICD#1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also delete file .travis.yml
, as Travis will not run any more and the focus is now fully on GitHub Actions
@riccardoporreca I have aligned the site.yml and deleted the travis.yml, let me know if anything else is required, otherwise you can go ahead with merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Refined comment about renv and fixed installation of remotes
with renv
as a final review.
I will commit the suggestions and squash-merge.
* Not necessarily Linux-specific * Mainly there in view of caching what we explicitly define as the renv root
* In general, we there is no guarantee of having remotes installed
Reviewed and updated shiny ci cd chapter, as well as the github actions yaml examples.
Closes #14.