Skip to content

Commit

Permalink
Switch to bolding for package names
Browse files Browse the repository at this point in the history
  • Loading branch information
@chartgerink
chartgerink committed May 6, 2024
1 parent b6b61c2 commit 3db5293
Show file tree
Hide file tree
Showing 4 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion code-review.qmd
View file
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ We have used two strategies for integrating suggestions in package reviews.

2. New feature branches can be created to make requested changes; each merged into the stable branch. Once all changes have been made in dedicated pull requests, the review pull request can be closed and the `review` branch deleted.

An [example of the first strategy can be found in the {finalsize} R package](https://github.com/epiverse-trace/finalsize/pull/161), and an [example of the second strategy can be found in the {superspreading} R package](https://github.com/epiverse-trace/superspreading/pull/31).
An [example of the first strategy can be found in the **finalsize** R package](https://github.com/epiverse-trace/finalsize/pull/161), and an [example of the second strategy can be found in the **superspreading** R package](https://github.com/epiverse-trace/superspreading/pull/31).

## Recognising contributions in reviews

Expand Down
2 changes: 1 addition & 1 deletion dependencies.qmd
View file
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ We embrace an [iterative development approach](principles.html#lean-and-agile-co

### Base R support schedule

We maintain a minimum support for the last four versions of R ([the {tidyverse} standard](https://www.tidyverse.org/blog/2019/04/r-version-support/)). The table outlines the concrete minimum supported version.
We maintain a minimum support for the last four versions of R ([the **tidyverse** standard](https://www.tidyverse.org/blog/2019/04/r-version-support/)). The table outlines the concrete minimum supported version.
Adopting the tidyverse standard allows us to use relatively recent R features, while putting a low pressure on our users to update their R version since they will already have to update to use the latest ggplot2 or tidyverse version.

| Year | Current R version | Minimum supported version |
Expand Down
4 changes: 2 additions & 2 deletions git-branching-merging.qmd
View file
Original file line number Diff line number Diff line change
Expand Up @@ -24,12 +24,12 @@ The R community in general sticks with a simple feature branch flow, and doesn't
| | - **unstable** `main` branch (development version) | - **unstable** `development` branch; |
| | - many feature branches originating from and being merged into `main` | - many feature branches originating from and being merged into `development` |
+--------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------+---------------------------------------------------------------------------------+
| installation instructions | The {real} package can be installed from CRAN with: | The {real} package can be installed from CRAN with: |
| installation instructions | The **real** package can be installed from CRAN with: | The **real** package can be installed from CRAN with: |
| | `install.packages("real")` | `install.packages("real")` |
| | You can also choose to install the development version of real from GitHub: | You can also choose to install the development version of real from GitHub: |
| | `remotes::install_github("epiverse-trace/real")` | `remotes::install_github("epiverse-trace/real@dev")` |
+--------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------+---------------------------------------------------------------------------------+
| use of the [{pkgdown} development mode](https://pkgdown.r-lib.org/reference/build_site.html#development-mode) to build two websites: | in the `_pkgdown.yml` file: | A custom `pkgdown.yml` GitHub Actions workflow setting the development mode to: |
| use of the [**pkgdown** development mode](https://pkgdown.r-lib.org/reference/build_site.html#development-mode) to build two websites: | in the `_pkgdown.yml` file: | A custom `pkgdown.yml` GitHub Actions workflow setting the development mode to: |
| | | |
| - released **stable** version | ``` yaml | - `dev` when triggered from the `development` branch |
| - development **unstable** version | development: | - `release` when triggered from the `main` branch |
Expand Down
2 changes: 1 addition & 1 deletion principles.qmd
View file
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ As an open-source initiative, Epiverse-TRACE will benefit from numerous other OS
- [From disconnected elements to a harmonious ecosystem: the Epiverse-TRACE project](https://epiverse-trace.github.io/slides/harmonious-ecosystem/)
- [Interoperability strategy for Epiverse](https://epiverse-trace.github.io/slides/interoperability-epiverse/)
- [Converting your R Function to an S3 Generic: benefits, pitfalls & design considerations](https://epiverse-trace.github.io/posts/s3-generic/)
- [Extending Data Frames: Creating custom classes and {dplyr} compatibility](https://epiverse-trace.github.io/posts/extend-dataframes/)
- [Extending Data Frames: Creating custom classes and **dplyr** compatibility](https://epiverse-trace.github.io/posts/extend-dataframes/)

:::

Expand Down

0 comments on commit 3db5293

Please sign in to comment.