Removing coveralls as it causes version constraint issues and there is only one test anyway

Author: carlio

.github/workflows/ci.yaml

@@ -148,50 +148,6 @@ jobs:
           name: coverage-${{ matrix.python-version }}
           path: .coverage
 
-  coverage:
-    name: Process test coverage
-    runs-on: ubuntu-latest
-    needs: ["prepare-tests-linux", "pytest-linux"]
-    strategy:
-      matrix:
-        python-version: ["3.13"]
-    env:
-      COVERAGERC_FILE: .coveragerc
-    steps:
-      - name: Check out code from GitHub
-        uses: actions/checkout@v3
-      - name: Set up Python ${{ matrix.python-version }}
-        id: python
-        uses: actions/setup-python@v4
-        with:
-          python-version: ${{ matrix.python-version }}
-      - name: Restore Python virtual environment
-        id: cache-venv
-        uses: actions/cache@v3
-        with:
-          path: venv
-          key:
-            ${{ runner.os }}-${{ steps.python.outputs.python-version }}-${{
-            needs.prepare-tests-linux.outputs.python-key }}
-      - name: Fail job if Python cache restore failed
-        if: steps.cache-venv.outputs.cache-hit != 'true'
-        run: |
-          echo "Failed to restore Python venv from cache"
-          exit 1
-      - name: Download all coverage artifacts
-        uses: actions/[email protected]
-      - name: Combine coverage results
-        run: |
-          . venv/bin/activate
-          coverage combine coverage*/.coverage
-          coverage report --rcfile=${{ env.COVERAGERC_FILE }}
-      - name: Upload coverage to Coveralls
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          . venv/bin/activate
-          coveralls --rcfile=${{ env.COVERAGERC_FILE }} --service=github
-
   prepare-tests-windows:
     name: Prepare tests for Python ${{ matrix.python-version }} (Windows)
     runs-on: windows-latest

.gitignore

@@ -38,6 +38,7 @@ htmlcov
 .pydevproject
 .pylint-plugin-utils
 .idea
+*.swp
 
 .venv
 env.txt

README.md

@@ -3,7 +3,6 @@
 ## Status
 
 [![Build Status](https://github.com/PyCQA/pylint-plugin-utils/actions/workflows/ci.yaml/badge.svg?branch=master)](https://github.com/PyCQA/pylint-plugin-utils/actions)
-[![Coverage Status](https://coveralls.io/repos/github/PyCQA/pylint-plugin-utils/badge.svg?branch=master)](https://coveralls.io/github/PyCQA/pylint-plugin-utils?branch=master)
 [![Code Style](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/ambv/black)
 [![Pypi Package version](https://img.shields.io/pypi/v/pylint-plugin-utils.svg)](https://pypi.python.org/pypi/pylint-plugin-utils)
 
@@ -26,12 +25,12 @@ pip install tox pytest
 
 To run the test suite for a particular Python version, you can do:
 ```bash
-tox -e py38
+tox -e py39
 ```
 
 To run individual tests with ``tox``, you can do:
 ```bash
-tox -e py38 -- -k test_linter_should_be_pickleable
+tox -e py39 -- -k test_linter_should_be_pickleable
 ```
 
 We use ``pytest`` for testing ``pylint``, which you can use without using ``tox`` for a faster development cycle.