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
devtools::check() # run R CMD check, which runs everything below
15
+
devtools::document() # generate package meta data and man files
16
16
devtools::test() # test package
17
-
devtools::check() # check package for errors
17
+
devtools::build_vignettes() # build vignettes only
18
+
devtools::run_examples() # run doc examples
19
+
devtools::check(vignettes=FALSE) # check package without vignettes
18
20
```
19
21
20
22
## Developing the documentation site
21
23
22
-
The [documentation site](https://cmu-delphi.github.io/epipredict/) is built off of the `main` branch. The `dev` version of the site is available at https://cmu-delphi.github.io/epipredict/dev.
23
-
24
-
The documentation site can be previewed locally by running in R
25
-
26
-
```r
27
-
pkgdown::build_site(preview=TRUE)
28
-
```
24
+
Our CI builds two versions of the documentation:
29
25
30
-
The `main` version is available at `file:///<local path>/epidatr/epipredict/index.html` and `dev` at `file:///<local path>/epipredict/docs/dev/index.html`.
26
+
-https://cmu-delphi.github.io/epipredict/ from the `main` branch and
27
+
-https://cmu-delphi.github.io/epipredict/dev from the `dev` branch.
31
28
32
-
You can also build the docs manually and launch the site with python. From the terminal, this looks like
29
+
Commands for developing the documentation site:
33
30
34
-
```bash
31
+
```sh
32
+
# Basic build and preview
35
33
R -e 'pkgdown::clean_site()'
36
34
R -e 'devtools::document()'
37
35
R -e 'pkgdown::build_site()'
38
-
python -m http.server -d docs
39
36
```
40
37
38
+
If you work without R Studio and want to iterate on documentation, you might
Please follow the guidelines in the [PR template document](.github/pull_request_template.md).
44
46
45
-
## Release process
47
+
## Planned CRAN release process
48
+
49
+
Open a release issue and then copy and follow this checklist in the issue (modified from the checklist generated by `usethis::use_release_issue(version = "1.0.2")`):
50
+
51
+
-[ ]`git pull` on `dev` branch.
52
+
-[ ] Make sure all changes are committed and pushed.
- Some [guidelines](https://style.tidyverse.org/news.html#news-release).
59
+
-[ ]`git checkout main`
60
+
-[ ]`git pull`
61
+
-[ ]`urlchecker::url_check()`.
62
+
- This may choke on the MIT license url, and that's ok.
63
+
-[ ]`devtools::build_readme()`
64
+
-[ ]`devtools::check_win_devel()`
65
+
-[ ] Have maintainer ("cre" in description) check email for problems.
66
+
-[ ]`revdepcheck::revdep_check(num_workers = 4)`.
67
+
- This may choke, it is very sensitive to the binary versions of packages on a given system. Either bypass or ask someone else to run it if you're concerned.
68
+
-[ ] Update `cran-comments.md`
69
+
-[ ] PR with any changes (and go through the list again) into `dev` and run through the list again.
70
+
71
+
Submit to CRAN:
72
+
73
+
-[ ]`devtools::submit_cran()`.
74
+
-[ ] Maintainer approves email.
75
+
76
+
Wait for CRAN...
46
77
47
-
TBD
78
+
-[ ] If accepted :tada:, move to next steps. If rejected, fix and resubmit.
79
+
-[ ] Open and merge a PR containing any updates made to `main` back to `dev`.
80
+
-[ ]`usethis::use_github_release(publish = FALSE)` (publish off, otherwise it won't push) will create a draft release based on the commit hash in CRAN-SUBMISSION and push a tag to the GitHub repo.
81
+
-[ ] Go to the repo, verify the release notes, and publish when ready.
0 commit comments