@@ -130,24 +130,28 @@ runs:
130130 PR_REF : ${{ github.event.pull_request.head.ref }}
131131 PR_REPO : ${{ github.event.pull_request.head.repo.full_name }}
132132 PR_REPO_ID : ${{ github.event.pull_request.base.repo.id }}
133- - name : Check out action repo
134- uses : actions/checkout@v4
135- with :
136- path : action-repo
137- ref : ${{ steps.set-repo-and-ref.outputs.ref }}
138- repository : ${{ steps.set-repo-and-ref.outputs.repo }}
139133 - name : Create Docker container action
140134 run : |
141135 # Create Docker container action
142- python create-docker-action.py
136+ python ${{ github.action_path }}/ create-docker-action.py
143137 env :
144138 REF : ${{ steps.set-repo-and-ref.outputs.ref }}
145139 REPO : ${{ steps.set-repo-and-ref.outputs.repo }}
146140 REPO_ID : ${{ steps.set-repo-and-ref.outputs.repo-id }}
147141 shell : bash
148- working-directory : action-repo
149142 - name : Run Docker container
150- uses : ./action-repo/.github/actions/run-docker-container
143+ # The generated trampoline action must exist in the allowlisted
144+ # runner-defined working directory so it can be referenced by the
145+ # relative path starting with `./`.
146+ #
147+ # This mutates the end-user's workspace slightly but uses a path
148+ # that is unlikely to clash with somebody else's use.
149+ #
150+ # We cannot use randomized paths because the composite action
151+ # syntax does not allow accessing variables in `uses:`. This
152+ # means that we end up having to hardcode this path both here and
153+ # in `create-docker-action.py`.
154+ uses : ./.github/.tmp/.generated-actions/run-pypi-publish-in-docker-container
151155 with :
152156 user : ${{ inputs.user }}
153157 password : ${{ inputs.password }}
0 commit comments