Skip to content

Updated documentation for CLion Setup #3240

Updated documentation for CLion Setup

Updated documentation for CLion Setup #3240

Triggered via pull request March 28, 2024 13:46
Status Success
Total duration 40s
Artifacts

pre-commit.yml

on: pull_request
pre-commit
34s
pre-commit
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
pre-commit
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-python@v2, pre-commit/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
pre-commit
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/
pre-commit
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/pull/881/merge, Key: pre-commit-2-94177efb2dcbbb1b3ae90e6f47f41a26a323c85c6a77e05f363a2d3d8b7cc270-5b1b7b0584400059f031752f542708327d8ddca051c5db8c6f5d30b113b8bf72, 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.