From 7ff1caf33291d1ed4001bebfa7342d5ad77eb3bf Mon Sep 17 00:00:00 2001 From: Ben Coleman Date: Fri, 24 Jul 2020 09:10:02 +0100 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0214d3d..a375361 100644 --- a/README.md +++ b/README.md @@ -23,7 +23,7 @@ The solution is to manually create a PAT and store it as a secret e.g. `${{ secr **Optional.** The inputs to pass to the workflow (if any are configured), this must be a JSON encoded string, e.g. `{ "myInput": "foobar" }` ### `ref` -**Optional.** The Git reference used with the triggered workflow run. The reference can be a branch, tag, or a commit SHA. If omitted the context ref of the triggering workflow is used +**Optional.** The Git reference used with the triggered workflow run. The reference can be a branch, tag, or a commit SHA. If omitted the context ref of the triggering workflow is used. If you want to trigger on pull requests and run the target workflow in the context of the pull request branch, set the ref to `${{ github.event.pull_request.head.ref }}` ### `repo` **Optional.** The default behavior is to trigger workflows in the same repo as the triggering workflow, if you wish to trigger in another GitHub repo "externally", then provide the owner + repo name with slash between them e.g. `microsoft/vscode`