@@ -130,24 +130,28 @@ runs:
130
130
PR_REF : ${{ github.event.pull_request.head.ref }}
131
131
PR_REPO : ${{ github.event.pull_request.head.repo.full_name }}
132
132
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 }}
139
133
- name : Create Docker container action
140
134
run : |
141
135
# Create Docker container action
142
- python create-docker-action.py
136
+ python ${{ github.action_path }}/ create-docker-action.py
143
137
env :
144
138
REF : ${{ steps.set-repo-and-ref.outputs.ref }}
145
139
REPO : ${{ steps.set-repo-and-ref.outputs.repo }}
146
140
REPO_ID : ${{ steps.set-repo-and-ref.outputs.repo-id }}
147
141
shell : bash
148
- working-directory : action-repo
149
142
- 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
151
155
with :
152
156
user : ${{ inputs.user }}
153
157
password : ${{ inputs.password }}
0 commit comments