You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: slides/05_publication.qmd
+79-10Lines changed: 79 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -20,9 +20,12 @@ author: Audrey T. Yeo
20
20
21
21
-`pkgdown` makes it quick and easy to build a website for your package
22
22
- After installing `pkgdown`, run `usethis::use_pkgdown()` to get started
23
+
- Alternatively, run `usethis::use_pkgdown_github_pages()`
24
+
- Adds (and writes) `pkgdown.yml`, `docs` folder, and "pkgdown" to `.Rbuildignore` and `docs` to `gitignore`. Also initialises empty branch `gh-pages` in chosen repo and activates GitHub Pages for repo [^1].
23
25
- Main configuration happens in `_pkgdown.yml` file
24
26
- Many customizations can be applied, but bulk of work during development is
25
27
updating the `reference` section with names of `.Rd` files
28
+
[^1]: `usethis::use_pkgdown_github_pages()` performs these actions additionally to `usethis::use_pkgdown()`.
26
29
27
30
## Example `_pkgdown.yml` File
28
31
@@ -198,19 +201,20 @@ rhub::rhub_platforms()
198
201
199
202
## GitHub Actions
200
203
201
-
- It is also possible to use GitHub Actions to run `R CMD check`
204
+
- It is also possible to use [GitHub Actions](https://docs.github.com/en/actions) to run `R CMD check`
202
205
- Free for public repositories, paid service for private repositories
203
206
- Checks will be run every time someone pushes a commit to a repository hosted on GitHub
204
207
- Easy setup from your R console: `usethis::use_github_action_check_standard()`
208
+
- ( runs a standard `R CMD check ` on three major operating systems. )
205
209
- Script and documentation are developed and maintained by the `r-lib` organization [here](https://github.com/r-lib/actions/tree/v2/check-r-package)
206
210
207
211
# GitHub
208
212
209
213
## Tags
210
214
211
215
- Tags are a feature of Git, i.e., not specific to GitHub
212
-
- Git can tag specific points in the code history as being important
213
-
- Typically, for each release, create a tag `vx.y.z`
216
+
- Git can tag (or "bookmark") specific points in the code history as being important
217
+
- Typically, for each release, create a tag `vx.y.z` (MAJOR.Minor.patch format)
214
218
- The value here is that users can later check out the package
215
219
in the state of this release version
216
220
- Download in R: `remotes::install_github("org/package", ref = "vx.y.z")`
@@ -222,12 +226,17 @@ rhub::rhub_platforms()
222
226
223
227
## Releases
224
228
225
-
-Based on Git tags, and a feature of GitHub
229
+
-[Releases](https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases) are based on Git tags, and a feature of GitHub
226
230
- Are "deployable software packages to make them available for a wider audience
227
231
to download and use"
228
232
- Contain release notes and links to the binary package files for download
229
233
- However, for R packages these `tar.gz` package files are rarely used
230
234
directly
235
+
236
+
```{Bash}
237
+
#| eval: false
238
+
git diff v0.3.14 v0.3.15 # checking for difference in mmrm release
239
+
```
231
240
232
241
## Releases: Example
233
242
@@ -239,7 +248,8 @@ rhub::rhub_platforms()
239
248
240
249
- The [Bioconductor](https://www.bioconductor.org/) project develops, supports,
241
250
and disseminates open source software for the analysis of biological assays
242
-
- Like CRAN, Bioconductor has additional package requirements
251
+
- Like CRAN, Bioconductor has additional package requirements.
252
+
One can only submit either to CRAN or Bioconductor.
243
253
- Packages are peer reviewed by community members
244
254
- New packages and updates to existing packages are released semi-annually
245
255
- Software is expected to be interoperable with other Bioconductor packages
- Run CRAN-like checks in RStudio: use `--as-cran` in check options
262
329
- Look at the CI/CD checks reported on your GitHub repository
263
330
- Where are the `R CMD check` results?
264
331
- Enable GitHub page through `use_pkgdown_github_pages`
332
+
- (nested in this [`use_pkgdown_github_pages`](https://pkgdown.r-lib.org/articles/pkgdown.html) includes : `use_pkgdown()`, `use_github_pages()`, `use_github_action("pkgdown")`)
265
333
- Deploy the website with `pkgdown`
266
-
- Need to change remote to `git`
267
-
- Deploy the website through `use_github_action("pkgdown")`
334
+
- Set up a GitHub action to deploy website `use_github_action("pkgdown")`
268
335
- (Optional) Check the automatic GitHub page deploy action
269
336
270
337
# License information {.smaller}
@@ -275,6 +342,8 @@ Use the same repository created from template [https://github.com/kkmann/simulat
275
342
- In the current version, changes were done by (later authors):
276
343
Liming Li [`r fontawesome::fa("github")`](https://github.com/clarkliming),
277
344
Philippe Boileau [`r fontawesome::fa("globe")`](https://pboileau.ca/),
0 commit comments