Skip to content

Catching AttributeError versus redirecting it to UnsupportedOperation #1073

Catching AttributeError versus redirecting it to UnsupportedOperation

Catching AttributeError versus redirecting it to UnsupportedOperation #1073

Triggered via push July 25, 2024 13:30
Status Success
Total duration 30s
Artifacts

giteesync.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
deploy
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
deploy
Unexpected input(s) 'run', valid inputs are ['entryPoint', 'args', 'ssh_private_key', 'target_repo']