This action runs a script in the post process. It is assumed that it will be called and used with a composite action that cannot perform post processing.
See action.yml
- name: Post Action
uses: srz-zumix/post-run-action@v3
with:
# custom shell
# Default : bash -e {0}
# bash : bash --noprofile --norc -eo pipefail {0}
# custom : e.g. `bash -l -ex {0}`
# see https://docs.github.com/ja/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsshell
shell: bash -ex {0}
# post run script text
post-run: |
echo "test" | tee "${{ runner.temp }}/test.txt"
if [ -f "${{ runner.temp }}/post.sh" ]; then
"${{ runner.temp }}/post.sh"
fi
- name: Post Action (Python)
id: test-python
uses: srz-zumix/post-run-action@v3
with:
shell: python
post-run: |
print("Hello, world!")
The post-run input is evaluated when the post step actually runs (during the post phase), not when the step is first processed.
This means that any expressions using ${{ ... }} syntax (e.g., ${{ env.MY_VAR }}) will capture the values at the time the post-run script executes,
reflecting any changes made during the workflow.
For example:
env:
MY_VAR: initial_value
steps:
- uses: srz-zumix/post-run-action@v3
with:
post-run: |
# ${{ env.MY_VAR }} is evaluated at post-run time
echo "Expression value: ${{ env.MY_VAR }}" # Will output: modified_value
echo "Environment value: $MY_VAR" # Will output: modified_value
- run: echo "MY_VAR=modified_value" >> "$GITHUB_ENV"In this example, even though MY_VAR is modified in a step after the post-run-action step is defined,
the expression ${{ env.MY_VAR }} will contain modified_value because it is evaluated when the post-run script actually executes (during the post phase).
Post Run Action is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.
Tags
(1)Post Run Action is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.