Skip to content
Pre-commit

fix: abp6 custom validation #3117

Sign in to view logs

fix: abp6 custom validation

fix: abp6 custom validation #3117

Triggered via pull request July 26, 2024 15:33
@daniel-belcherdaniel-belcher
synchronize #686
cust-val-wfgen
Status Success
Total duration 31s
Artifacts –

pre-commit.yml

on: pull_request
prettier
23s
prettier
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
prettier
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
prettier
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, 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/
prettier
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/pull/686/merge, Key: pre-commit-2-d67abd8acd75706dba52f9750e7e5b8804e3c1f1969c7ca81bf1f04731adc369-de18ce03edd69691798ac091e04466267763359dc891d443c23b2caf1df640e4, 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.