Skip to content

feat: add support for restricting the deleted files output to only deleted directories #10764

feat: add support for restricting the deleted files output to only deleted directories

feat: add support for restricting the deleted files output to only deleted directories #10764

Status Success
Total duration 24m 4s
Artifacts 1

test.yml

on: pull_request
Test with multiple repositories
19s
Test with multiple repositories
Test changed-files using since and until
0s
Test changed-files using since and until
Test changed-files similar base and commit sha
9s
Test changed-files similar base and commit sha
Test unset GITHUB_OUTPUT env
12s
Test unset GITHUB_OUTPUT env
Test changed-files with pull request head ref
7s
Test changed-files with pull request head ref
Test changed-files non existent base sha
12s
Test changed-files non existent base sha
Test changed-files non existent sha
33s
Test changed-files non existent sha
Test changed-files with REST API
13s
Test changed-files with REST API
Test dir names deleted files include only deleted dirs single file
8s
Test dir names deleted files include only deleted dirs single file
Test dir names deleted files include only deleted dirs
9s
Test dir names deleted files include only deleted dirs
Matrix: Test changed-files with limited commit history
Matrix: Test changed-files with pull request without persist credentials
Matrix: Test changed-files recover deleted file
Matrix: Test changed-files since last remote commit
Matrix: Test changed-files with submodule
Matrix: Test changed-files with yaml
Matrix: Test changed-files
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 27 warnings
Test changed-files similar base and commit sha
Similar commit hashes detected: previous sha: d1c0ee4 is equivalent to the current sha: d1c0ee4.
Test changed-files similar base and commit sha
Please verify that both commits are valid, and increase the fetch_depth to a number higher than 50.
Test changed-files similar base and commit sha
Similar commit hashes detected.
Test changed-files non existent base sha
Unable to locate the commit sha: 4554456
Test changed-files non existent base sha
Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed
Test changed-files non existent base sha
The process '/usr/bin/git' failed with exit code 128
Test changed-files non existent base sha
Unable to locate the commit sha: 4554456
Test changed-files non existent base sha
Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed
Test changed-files non existent base sha
The process '/usr/bin/git' failed with exit code 128
Test changed-files non existent sha
Unable to locate the commit sha: 4774456
Test changed-files non existent sha
Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed
Test changed-files non existent sha
Unable to determine a difference between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da..4774456
Test changed-files non existent sha
Unable to locate the commit sha: 4774456
Test changed-files non existent sha
Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed
Test changed-files non existent sha
Unable to determine a difference between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da..4774456
Test changed-files since last remote commit (1)
Unable to locate the previous commit in the local history. Please ensure to checkout pull request HEAD commit instead of the merge commit. See: https://github.com/actions/checkout/blob/main/README.md#checkout-pull-request-head-commit-instead-of-merge-commit
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Test changed-files non existent base sha
fatal: ambiguous argument '4554456...d2486b470f2ea6ffb0bc55a779968d797a2e3009': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'
Test changed-files non existent base sha
fatal: ambiguous argument '4554456...d2486b470f2ea6ffb0bc55a779968d797a2e3009': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]'
Test changed-files with limited commit history (1, 1)
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and d2486b470f2ea6ffb0bc55a779968d797a2e3009
Test changed-files with limited commit history (1, 2)
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and d2486b470f2ea6ffb0bc55a779968d797a2e3009
Test changed-files with limited commit history (2, 1)
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and d2486b470f2ea6ffb0bc55a779968d797a2e3009
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files non existent sha
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and 4774456
Test changed-files with limited commit history (2, 2)
Unable to find merge base between 72d7089b7241aaa6c60dc39e8336f9aef5ebd1da and d2486b470f2ea6ffb0bc55a779968d797a2e3009

Artifacts

Produced during runtime
Name Size
build-assets Expired
3.34 MB