Skip to content
CI

chore: add test for detecting changed-files in a nested directory #13903

Sign in to view logs

chore: add test for detecting changed-files in a nested directory

chore: add test for detecting changed-files in a nested directory #13903

Triggered via pull request March 7, 2024 21:27
@jackton1jackton1
synchronize #1972
chore/add-test-for-detecting-changed-files-in-a-nested-directory
Status Success
Total duration 5m 48s
Artifacts 1

test.yml

on: pull_request
build
50s
build
Test with multiple repositories
17s
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
10s
Test changed-files similar base and commit sha
Test using branch names for base_sha and sha inputs
11s
Test using branch names for base_sha and sha inputs
Test changed-files with pull request head ref
5s
Test changed-files with pull request head ref
Test changed-files non existent base sha
10s
Test changed-files non existent base sha
Test changed-files non existent sha
10s
Test changed-files non existent sha
Test changed-files with REST API
5s
Test changed-files with REST API
Test changed-files with dir-names in a nested folder
7s
Test changed-files with dir-names in a nested folder
Test changed-files with non existing repository
0s
Test changed-files with non existing repository
Test dir names deleted files include only deleted dirs single file
15s
Test dir names deleted files include only deleted dirs single file
Test dir names deleted files include only deleted dirs
7s
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

9 errors and 4 warnings
build
Process completed with exit code 1.
Test changed-files similar base and commit sha
Similar commit hashes detected: previous sha: d1c0ee4e67338c2c3e50a08b6156ab8c155be21c is equivalent to the current sha: d1c0ee4e67338c2c3e50a08b6156ab8c155be21c.
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
Test changed-files non existent base sha
Test changed-files non existent sha
Test changed-files non existent sha
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
Input "sha" is not supported when using GitHub's REST API to get changed files
Test changed-files with limited commit history (1, 2)
Unable to find merge base between a65c2f2100bbf5456ab3003d2f2f8694a766ca15 and 61c8f3e04f2d97e7822cd184f4a54ed2c75648c2
Test changed-files with limited commit history (1, 1)
Unable to find merge base between a65c2f2100bbf5456ab3003d2f2f8694a766ca15 and 61c8f3e04f2d97e7822cd184f4a54ed2c75648c2
Test changed-files since last remote commit (1)
Unable to locate the commit sha: 693824960ad30ecd3b7381e7400124989e594e27

Artifacts

Produced during runtime
Name Size
build-assets Expired
927 KB