Skip to content

Add LeanRL as a related project #1403

Add LeanRL as a related project

Add LeanRL as a related project #1403

Triggered via pull request September 24, 2024 16:16
Status Success
Total duration 1m 7s
Artifacts

pre-commit.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
build (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, pre-commit/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, pre-commit/[email protected]. 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.9)
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/pull/484/merge, Key: pre-commit-2-0ca8ea8eb1a70b4c22278e1d98390ce5586a07fb265de350fc85bc182ededcd8-a70e8b98f9a2bc623eefa6e54ca88fd88e4fb7a57bf2dda65748354fa034b84e, Version: 25d34710bdd63bed70a22b8204c3e1d0942dc237e098600e3896b4334c6d784f This only has performance implications and won't change the result of your pre-commit tests. If this problem persists on your default branch, you can try to fix it by editing your '.pre-commit-config.yaml'. For example try to run 'pre-commit autoupdate' or simply add a blank line. This will result in a different hash value and thus a different cache target.