Add a coverage test when pushing to master

[GarethCabournDavies]

Add a coverage test. So that it isn't run too often, Ive set it so that it will run on pushes to master rather than for all events in a PR (unless its got a specific label, I think I set this up correctly)

This is largely based on the process used by gwpy

Standard information about the request

This is a new feature in the CI

This changehas been proposed using the contribution guidelines

Motivation

So that we are regularly reminded of the importance of testing!

Contents

A new GitHub job

Testing performed

The coverage test works locally and produces a html page with a table of the coverage for each module under pycbc. I have no idea if it will run in the CI, as I think this will use the rules of master to decide whether to turn the test or not, for a test which doesn't exist in master

• The author of this pull request confirms they will adhere to the code of conduct

[Copilot]

Pull request overview

This PR adds a code coverage test job to the GitHub Actions CI workflow. The coverage job is configured to run on pushes to the master branch or on pull requests that have been labeled with 'coverage', allowing coverage testing without running it on every PR event.

Changes:

• Renamed workflow from "Flake8 check" to "Code quality checks"
• Modified workflow triggers to run on push to master and various PR events
• Added a new coverage job that installs dependencies, runs tests with coverage tracking, generates an HTML report, and uploads it as an artifact

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.