Skip to content

Improving download performance when cloning based on specific branches or tags #409

Improving download performance when cloning based on specific branches or tags

Improving download performance when cloning based on specific branches or tags #409

Re-run triggered October 6, 2024 11:09
Status Failure
Total duration 1m 14s
Artifacts

pull-request.yml

on: pull_request
check-commit-message  /  Check Commit Message
5s
check-commit-message / Check Commit Message
reuse
8s
reuse
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
check-commit-message / Check Commit Message
fd6a7a1c13d34b010c0c0a97350b75fdebdc1db4 Subject too long (max 50)
build (3.8)
Process completed with exit code 2.
reuse
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check-commit-message / Check Commit Message
The following actions use a deprecated Node.js version and will be forced to run on node20: tim-actions/get-pr-commits@master, tim-actions/commit-message-checker-with-regex@v0.3.2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (3.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/