https://github.com/pachadotdev/eodr
https://github.com/pachadotdev/eodr
Last synced: about 1 year ago
JSON representation
- Host: GitHub
- URL: https://github.com/pachadotdev/eodr
- Owner: pachadotdev
- License: other
- Created: 2021-01-27T23:52:49.000Z (over 5 years ago)
- Default Branch: main
- Last Pushed: 2021-01-29T11:32:45.000Z (over 5 years ago)
- Last Synced: 2025-03-20T20:19:16.111Z (over 1 year ago)
- Language: R
- Size: 1.36 MB
- Stars: 0
- Watchers: 1
- Forks: 9
- Open Issues: 0
-
Metadata Files:
- Readme: README.Rmd
- Contributing: .github/CONTRIBUTING.md
- License: LICENSE
- Code of conduct: .github/CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
---
output: github_document
---
```{r, include = FALSE}
knitr::opts_chunk$set(
collapse = TRUE,
comment = "#>",
fig.path = "man/figures/README-",
out.width = "100%"
)
```
# eodr
[](https://www.tidyverse.org/lifecycle/#experimental)
[](https://CRAN.R-project.org/package=eodr)
The goal of eodr is to ...
## Installation
You can install the released version of eodr from [CRAN](https://CRAN.R-project.org) with:
``` r
install.packages("eodr")
```
## Example
This is a basic example which shows you how to solve a common problem:
```{r example}
library(eodr)
## basic example code
```
What is special about using `README.Rmd` instead of just `README.md`? You can include R chunks like so:
```{r cars}
summary(cars)
```
You'll still need to render `README.Rmd` regularly, to keep `README.md` up-to-date. `devtools::build_readme()` is handy for this. You could also use GitHub Actions to re-render `README.Rmd` every time you push. An example workflow can be found here: .
You can also embed plots, for example:
```{r pressure, echo = FALSE}
plot(pressure)
```
In that case, don't forget to commit and push the resulting figure files, so they display on GitHub and CRAN.