-
Notifications
You must be signed in to change notification settings - Fork 0
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
DEV_website attempt #2
Conversation
Task linked: CU-868703b5w build website |
hi @giorgiacek , I think it makes sense to merge into DEV once the examples of all functions are ready and, ideally, the vignettes as well. We don't really need to merge into |
hi @randrescastaneda, yes it makes sense. I think I am done now with gd_functions and md_functions. And I am drafting the vignettes. So I switched to DEV_website. I assume: you (or should I?) will merge both (gd_examples and md_examples) into DEV_website, I start working on DEV_website, I push to deployment through DEV_website. |
Hi @giorgiacek, Thanks. |
Gd functions -> DEV_website
DEV changes merged into DEV_website
… user-specified mean when needed
Dev website mean
…igth output when popshare = user defined number.
Dev website params
…params Revert 15 dev website params
Not sure it make sense to PR, nothing has changed, I just added DEV_website to the YAML so that my commits should have triggered the pkgdown workflow directly (they do, but the workflow which adds to gh-pages fails). But after the PR we should then add DEV to the YAML.