Skip to content

fix: solve the conflict #124

fix: solve the conflict

fix: solve the conflict #124

Triggered via push September 1, 2023 15:58
Status Success
Total duration 1m 19s
Artifacts

lint.yml

on: push
Check code formatting with Black
15s
Check code formatting with Black
Check valid import formatting with isort
12s
Check valid import formatting with isort
Check valid formatting with flake8
9s
Check valid formatting with flake8
Check that pre-commit hooks pass
1m 9s
Check that pre-commit hooks pass
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Check valid formatting with flake8
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Check valid import formatting with isort
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Check code formatting with Black
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Check that pre-commit hooks pass
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/