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: README.md
+40
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,8 @@ Then trigger it manually using the 'run workflow' button under the actions tab.
33
33
34
34
A summary of the results can be seen in the GHA webUI. Upon completion, the full install/check logs for all packages are available in the 'artifacts' section.
35
35
36
+
See [Advanced Usage](#advanced-usage) for information on additional workflow arguments recheck supports.
37
+
36
38
## Real world example
37
39
38
40
See here for an example using the V8 package: https://github.com/jeroen/V8/actions/workflows/recheck.yaml
@@ -59,3 +61,41 @@ CRAN runs revdep checks on `r-devel` on a server with `debian:testing` but there
59
61
60
62
On GitHub actions we run the check inside the [rcheckserver](https://github.com/r-devel/rcheckserver)
61
63
container. This container has the same system libraries installed as the CRAN Debian server.
64
+
65
+
## Advanced Usage
66
+
67
+
By default, recheck runs against the package in the current repository.
68
+
For some use cases, it may be useful to run recheck against a repository other than the current one and/or against a branch other than the default.
69
+
70
+
This can be achieved through a combination of the `repo` and `ref` parameters:
71
+
72
+
- `repo`: Repository to checkout (as `owner/repo`)
73
+
- `ref`: The branch, tag or SHA to checkout
74
+
75
+
See the following example to get an idea of what this can look like:
0 commit comments