From 4a6d622f66c6e56d0d043103514281db081a373f Mon Sep 17 00:00:00 2001 From: Josh Johanning Date: Wed, 31 Aug 2022 23:09:36 -0500 Subject: [PATCH] Fix misleading example of reusable workflows (#20324) Co-authored-by: Lucas Costi --- content/actions/using-workflows/reusing-workflows.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/actions/using-workflows/reusing-workflows.md b/content/actions/using-workflows/reusing-workflows.md index 521ed4ea33..676a5f6f41 100644 --- a/content/actions/using-workflows/reusing-workflows.md +++ b/content/actions/using-workflows/reusing-workflows.md @@ -127,7 +127,7 @@ You can define inputs and secrets, which can be passed from the caller workflow runs-on: ubuntu-latest environment: production steps: - - uses: ./.github/workflows/my-action + - uses: octo-org/my-action@v1 with: username: ${{ inputs.username }} token: ${{ secrets.envPAT }} @@ -168,12 +168,13 @@ jobs: name: Pass input and secrets to my-action runs-on: ubuntu-latest steps: - - uses: ./.github/workflows/my-action + - uses: octo-org/my-action@v1 with: username: ${{ inputs.username }} token: ${{ secrets.token }} ``` {% endraw %} + {% ifversion actions-reusable-workflow-matrix %} ## Using a matrix strategy with a reusable workflow