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
* Instead of reading them as code chunks and rendering them via `{yml}`, use inline R expressions as suggested at <https://stackoverflow.com/a/67815701>.
* We still read all workflow files upfront to streamline the approach and leverage this for the "ci-cd.yml" workflow included twice.
* Consistent usage of `yaml` as plain-markdown fenced block language.
The `steps` described in the previous section are defined in the `.yml` workflow file as follows:
101
104
102
-
```{yml ci-cd.yml}
105
+
```yaml
106
+
`r workflows_content["ci-cd.yml"]`
103
107
```
104
108
105
109
As visible from the run logs that can be found in the GitHub repository under the `Actions` tab, all the CI/CD pipeline steps are performed subsequently, and are identifiable by the `name` field. See the example below, showing how the deployment step is skipped for a run not triggered by a push action the `main` (or `master`) branch:
@@ -127,25 +131,29 @@ usethis::use_github_actions_badge("ci-cd.yml") # or "ci.yml"/"ci(-cd)-renv.yml"
0 commit comments