-
Notifications
You must be signed in to change notification settings - Fork 16
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
tic #111
Conversation
Codecov Report
@@ Coverage Diff @@
## master #111 +/- ##
=========================================
Coverage ? 57.32%
=========================================
Files ? 12
Lines ? 635
Branches ? 0
=========================================
Hits ? 364
Misses ? 271
Partials ? 0
Continue to review full report at Codecov.
|
Maybe the dirs could be less flexible, i.e. having analysis, data and outputs by default, and using the dirs arguments only for creating supplemental directories? |
@stephlocke current questions
|
Examples of deployed report https://maelle.github.io/newtest.lockedata.starters/analysis1.html repo https://github.com/maelle/newtest.lockedata.starters |
both - different render types tho |
Looks fine to me |
I think |
Expected to address #4 #5 #85
What's missing are the custom tic.R templates for training, analysis and basic projects.
not sure what should be in a basic project tic.R
in training and analysis the idea will "simply" be to knit things from a folder and store them somewhere (that folder? a branch?) but I'm stuck because the directories can be set by the user, so it's hard to know which one has the Rmd to knit. Thoughts @stephlocke?