You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Review using black, ruff formatter, or similar to consistently format codebase. Note that idna-data make-libdata needs to generate code fragments that conform with this style.
The text was updated successfully, but these errors were encountered:
You might start using super-linter in a test workflow.
steps:
- name: Checkout
uses: actions/checkout@v4
with:
fetch-depth: 0
persist-credentials: false
- name: Super Linter Code Base
uses: github/super-linter/slim@v5
env:
FILTER_REGEX_INCLUDE: "/hexonet/*|/scripts/*|updateVersion.sh|setup.py"
VALIDATE_PYTHON_BLACK: true
# further linters on demand e.g. VALIDATE_BASH: true
VALIDATE_ALL_CODEBASE: false
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
That is at least validating newly touched files using Black. It is not auto-reformatting. That's something you would to cover through your IDE the best (e.g. VSCode, ms-python.black-formatter extension).
You may dive into adding a .devcontainer folder with respective files (Dockerfile, devcontainer.json, ...) to add a Python-based Dev Container to have always a working environment at hand which is handy if you switch to another device. You just need docker. VSCode automatically starts the container up and you can directly develop in there.
Review using black, ruff formatter, or similar to consistently format codebase. Note that idna-data make-libdata needs to generate code fragments that conform with this style.
Review using
black
,ruff
formatter, or similar to consistently format codebase. Note thatidna-data make-libdata
needs to generate code fragments that conform with this style.The text was updated successfully, but these errors were encountered: