Updated README.md #9861

Triggered via pull request August 30, 2023 17:29

tj-actions-bot

synchronize #1510

chore/update-readme

Status Success

Total duration 11m 14s

Artifacts 1

test.yml

on: pull_request

build

59s

Run shellcheck

Test with multiple repositories

13s

Test changed-files using since and until

Test changed-files similar base and commit sha

Test unset GITHUB_OUTPUT env

Test changed-files with pull request head ref

Test changed-files non existent base sha

13s

Test changed-files non existent sha

21s

Test changed-files with REST API

10s

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 with submodule

Matrix: Test changed-files with yaml

Matrix: Test changed-files

Annotations

33 errors and 31 warnings

Test changed-files (macos-latest, 0)

Unable to locate the commit sha: 90e2f25187c8ba157f3064d61a402e577bf6b026

Test changed-files (macos-latest, 0)

Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed

Test changed-files (macos-latest, 1)

Unable to locate the commit sha: 90e2f25187c8ba157f3064d61a402e577bf6b026

Test changed-files (macos-latest, 1)

Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed

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 ef21b845077a6a12523c59bee84fab2847a3c6ed..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 ef21b845077a6a12523c59bee84fab2847a3c6ed..4774456

Test changed-files (ubuntu-latest, 0)

Unable to locate the commit sha: 90e2f25187c8ba157f3064d61a402e577bf6b026

Test changed-files (ubuntu-latest, 0)

Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed

Test changed-files (ubuntu-latest, 2)

Unable to locate the commit sha: 90e2f25187c8ba157f3064d61a402e577bf6b026

Test changed-files (ubuntu-latest, 2)

Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed

Test changed-files (ubuntu-latest, 1)

Unable to locate the commit sha: 90e2f25187c8ba157f3064d61a402e577bf6b026

Test changed-files (ubuntu-latest, 1)

Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed

Test changed-files (macos-latest, 2)

Unable to locate the commit sha: 90e2f25187c8ba157f3064d61a402e577bf6b026

Test changed-files (macos-latest, 2)

Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed

Test changed-files (windows-latest, 1)

Unable to locate the commit sha: 90e2f25187c8ba157f3064d61a402e577bf6b026

Test changed-files (windows-latest, 1)

Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed

Test changed-files (windows-latest, 0)

Unable to locate the commit sha: 90e2f25187c8ba157f3064d61a402e577bf6b026

Test changed-files (windows-latest, 0)

Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed

Test changed-files (windows-latest, 2)

Unable to locate the commit sha: 90e2f25187c8ba157f3064d61a402e577bf6b026

Test changed-files (windows-latest, 2)

Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed

Test changed-files (macos-latest, 0)

Unable to locate the remote branch head sha. Falling back to the previous commit in the local history.

Test changed-files (macos-latest, 1)

Unable to locate the remote branch head sha. Falling back to the previous commit in the local history.

Test changed-files non existent base sha

fatal: ambiguous argument '4554456...da097b07a41fc0d398e79476f53ab3a8c9e9549d': 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

Test changed-files non existent sha