Avoid cross-job artifacts; combine coverage with --cov-append.

Gitea artifact download is unreliable with v3 actions, so the report job re-runs both suites on one runner after parallel test gates pass.

Co-authored-by: Cursor <[email protected]>

.gitea/workflows/test.yml

@@ -27,17 +27,7 @@ jobs:
         run: uv sync --all-extras
 
       - name: Run unit tests
-        run: |
+        run: uv run pytest tests/unit/ -m "not integration" -v
-          uv run pytest tests/unit/ -m "not integration" \
-            --cov=python_repositories \
-            --cov-report=
-
-      - name: Upload unit coverage
-        uses: actions/upload-artifact@v3
-        with:
-          name: coverage-unit
-          path: .coverage
-          retention-days: 1
 
   integration-tests:
     runs-on: ubuntu-latest
@@ -62,17 +52,7 @@ jobs:
         run: docker info
 
       - name: Run integration tests
-        run: |
+        run: uv run pytest -m integration -v
-          uv run pytest -m integration \
-            --cov=python_repositories \
-            --cov-report=
-
-      - name: Upload integration coverage
-        uses: actions/upload-artifact@v3
-        with:
-          name: coverage-integration
-          path: .coverage
-          retention-days: 1
 
   coverage-report:
     needs: [unit-tests, integration-tests]
@@ -95,22 +75,17 @@ jobs:
           UV_LINK_MODE: copy
         run: uv sync --all-extras
 
-      - name: Download unit coverage
+      # Gitea Actions lacks cross-job artifact download APIs; re-run tests here
-        uses: actions/download-artifact@v3
+      # with --cov-append on one runner for an accurate combined report.
-        with:
+      - name: Run tests with combined coverage
-          name: coverage-unit
-          path: coverage-unit
-
-      - name: Download integration coverage
-        uses: actions/download-artifact@v3
-        with:
-          name: coverage-integration
-          path: coverage-integration
-
-      - name: Combine coverage report
         run: |
-          uv run coverage combine coverage-unit/.coverage coverage-integration/.coverage
+          uv run pytest tests/unit/ -m "not integration" \
-          uv run coverage report -m --include='python_repositories/*' > coverage.txt
+            --cov=python_repositories \
+            --cov-report=
+          uv run pytest -m integration \
+            --cov=python_repositories \
+            --cov-append \
+            --cov-report=term-missing > coverage.txt
           cat coverage.txt
 
       - name: Post coverage summary to PR

README.md

@@ -148,7 +148,7 @@ uv run pytest -v                                      # full suite (requires Doc
 
 Integration tests are marked with `@pytest.mark.integration` and require Docker (testcontainers). Run unit tests alone for quick local feedback.
 
-CI runs unit and integration tests in parallel, then merges coverage into a single report (see [`.gitea/workflows/test.yml`](.gitea/workflows/test.yml)).
+CI runs unit and integration tests in parallel for fast feedback; a follow-up job re-runs both suites with `--cov-append` to produce a combined coverage report (Gitea Actions does not support cross-job artifact download yet).
 
 `pre-commit` is included in the dev dependency group. `uv sync` installs the CLI, but git does not run hooks until you install them with `pre-commit install` (one time per clone). After that, commits run the checks defined in [`.pre-commit-config.yaml`](.pre-commit-config.yaml) (ruff, mypy, pyupgrade, prettier, and general file hygiene).