Skip to content
Testing

Add Challenge.clone staticmethod to clone challenges from remote #63

Sign in to view logs

Add Challenge.clone staticmethod to clone challenges from remote

Add Challenge.clone staticmethod to clone challenges from remote #63

Triggered via push August 20, 2024 18:16
@ColdHeatColdHeat
pushed 2ea8358
challenge-mirror-all
Status Success
Total duration 31s
Artifacts –

test.yml

on: push
Matrix: Testing
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Testing (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/
Testing (3.10)
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/
Testing (3.11)
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/
Testing (3.9)
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/