Get All Changed Files
ActionsTags
(2)
Get all of the files changed/modified in a pull request or push's commits.
You can choose to get all changed files, only added files, only modified files, only removed files, only renamed files, or all added and modified files.
These outputs are available via the steps output context.
The steps output context exposes the output names all, added, modified, removed, renamed, and added_modified.
See action.yml
- uses: jitterbit/get-changed-files@v1
with:
# Format of the steps output context.
# Can be 'space-delimited', 'csv', or 'json'.
# Default: 'space-delimited'
format: ''- Get all changed files as space-delimited
- Get all added and modified files as CSV
- Get all removed files as JSON
If there are any files with spaces in them, then this method won't work and the step will fail. Consider using one of the other formats if that's the case.
- id: files
uses: jitterbit/get-changed-files@v1
- run: |
for changed_file in ${{ steps.files.outputs.all }}; do
echo "Do something with this ${changed_file}."
done- id: files
uses: jitterbit/get-changed-files@v1
with:
format: 'csv'
- run: |
mapfile -d ',' -t added_modified_files < <(printf '%s,' '${{ steps.files.outputs.added_modified }}')
for added_modified_file in "${added_modified_files[@]}"; do
echo "Do something with this ${added_modified_file}."
done- id: files
uses: jitterbit/get-changed-files@v1
with:
format: 'json'
- run: |
readarray -t removed_files <<<"$(jq -r '.[]' <<<'${{ steps.files.outputs.removed }}')"
for removed_file in ${removed_files[@]}; do
echo "Do something with this ${removed_file}."
doneMake sure to do the following before checking in any code changes.
$ yarn
$ yarn allThe scripts and documentation in this project are released under the MIT License
Get All Changed Files 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
(2)Get All Changed Files 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.