Skip to content

πŸ–‡ add structure to info rules (#455) #364

πŸ–‡ add structure to info rules (#455)

πŸ–‡ add structure to info rules (#455) #364

Workflow file for this run

---
name: release
on:
push:
branches:
- main
env:
PYTHON_VERSION: "3.11"
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-python@v4
with:
python-version: ${{ env.PYTHON_VERSION }}
# The installation is required as mypy must be run in the local system environment, not in the pre-commit environment.
- name: Install required dependencies
run: |
python3 -m pip install --upgrade pip poetry
poetry config virtualenvs.create false
poetry install -E all
- name: Linting and static code checks
run: |
pre-commit run --all-files
tests:
runs-on: ubuntu-latest
environment: CD
steps:
- uses: actions/checkout@v3
- uses: actions/setup-python@v4
with:
python-version: ${{ env.PYTHON_VERSION }}
- name: Install core dependencies
run: |
python3 -m pip install --upgrade pip poetry
poetry config virtualenvs.create false
poetry install -E all
- name: Test
env:
CI: 1
run: pytest
- uses: codecov/codecov-action@v3
with:
file: ./coverage.xml
- name: Build package
run: poetry build
- name: Release to PyPI
env:
TWINE_USERNAME: __token__
TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
run: twine upload --verbose dist/* || echo 'Version exists'