CI: testing impact of poetry.lock (#92)

* CI: testing impact of poetry.lock

* attempt at caching the installed dependencies

* figuring out the correct syntax

* test

* fix?

* Empty-Commit: test caching

* caching without commiting poetry.lock

* syntax

* should not use old caches: otherwise we always use the same old lock file

* bump mypy to cause cache miss

* on cache miss: keep venv but delete old poetry.lock

* delete lock file on cache miss

Author: twoertwein

.github/workflows/test.yml

@@ -26,6 +26,27 @@ jobs:
     - name: Install Poetry
       run: pip install poetry
 
+    - name: Determine poetry cache-dir
+      run: |
+        echo "::set-output name=PATH::$(poetry config cache-dir)"
+      id: cache_path
+
+    - name: Cache project dependencies
+      id : cache
+      uses: actions/cache@v3
+      with:
+        path: |
+          ${{ steps.cache_path.outputs.PATH }}
+          poetry.lock
+        key: ${{ matrix.os }}-${{ matrix.python-version }}-poetry-${{ hashFiles('pyproject.toml') }}
+        restore-keys: ${{ matrix.os }}-${{ matrix.python-version }}-poetry-
+
+    - name: Delete poetry.lock on cache miss
+      if: steps.cache.outputs.cache-hit != 'true'
+      uses: JesseTG/[email protected]
+      with:
+        path: poetry.lock
+
     - name: Install project dependencies
       run: poetry install -vvv --no-root
 

pyproject.toml

@@ -36,7 +36,7 @@ python = ">=3.8,<3.11"
 [tool.poetry.dev-dependencies]
 mypy = ">=0.960"
 pytest = ">=7.1.2"
-pyright = ">=1.1.251"
+pyright = ">=1.1.255"
 poethepoet = ">=0.13.1"
 loguru = ">=0.6.0"
 pandas = "1.4.3"