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::document() # generate package meta data and man files
7
7
devtools::build() # build package
8
-
9
8
```
10
9
11
10
## Validating the package
@@ -20,41 +19,31 @@ devtools::check() # check package for errors
20
19
21
20
## Developing the documentation site
22
21
23
-
The [documentation site](https://cmu-delphi.github.io/epidatr/) is built off of the `main` branch. The `dev` version of the site is available at https://cmu-delphi.github.io/epidatr/dev.
22
+
Our CI builds two version of the documentation:
23
+
24
+
-https://cmu-delphi.github.io/epidatr/ from the `main` branch and
25
+
-https://cmu-delphi.github.io/epidatr/dev from the `dev` branch.
24
26
25
-
The documentation site can be previewed locally by running in R
27
+
The documentation site can be previewed locally by running in R:
26
28
27
29
```r
30
+
# Should automatically open a browser
28
31
pkgdown::build_site(preview=TRUE)
29
32
```
30
33
31
-
The `main` version is available at `file:///<local path>/epidatr/docs/index.html` and `dev` at `file:///<local path>/epidatr/docs/dev/index.html`.
34
+
If the above does not open a browser, you can try using a Python server from the
35
+
command line:
32
36
33
-
You can also build the docs manually and launch the site with python. From the terminal, this looks like
34
37
```bash
35
38
R -e 'devtools::document()'
39
+
R -e 'pkgdown::build_site()'
36
40
python -m http.server -d docs
37
41
```
38
42
39
-
For `pkgdown` to correctly generate both public (`main`) and `dev` documentation sites, the package version in `DESCRIPTION` on `dev` must have four components, and be of the format `x.x.x.9000`. The package version on `main` must be in the format `x.x.x`.
43
+
## Versioning
40
44
41
-
The documentation website is updated on push or pull request to the `main` and `dev` branches.
45
+
Please follow the guidelines in the [PR template document](.github/pull_request_template.md).
42
46
43
47
## Release process
44
48
45
-
### Manual
46
-
47
49
TBD
48
-
49
-
### Automated (currently unavailable)
50
-
51
-
The release consists of multiple steps which can be all done via the GitHub website:
52
-
53
-
1. Go to [create_release GitHub Action](https://github.com/cmu-delphi/epidatr/actions/workflows/create_release.yml) and click the `Run workflow` button. Enter the next version number or one of the magic keywords (patch, minor, major) and hit the green `Run workflow` button.
54
-
2. The action will prepare a new release and will end up with a new [Pull Request](https://github.com/cmu-delphi/epidatr/pulls)
55
-
3. Let the code owner review the PR and its changes and let the CI check whether everything builds successfully
56
-
4. Once approved and merged, another GitHub action job starts which automatically will
57
-
1. create a git tag
58
-
2. create another [Pull Request](https://github.com/cmu-delphi/epidatr/pulls) to merge the changes back to the `dev` branch
59
-
3. create a [GitHub release](https://github.com/cmu-delphi/epidatr/releases) with automatically derived release notes
0 commit comments