The current testing and coverage analysis pipeline is implemented via Travis, but to avoid potential fees we should migrate it over to GitHub Actions. This should be almost as straightforward as copying across the relevant configuration from a currently set-up repo (see e.g. pyrolite workflows).
The current testing and coverage analysis pipeline is implemented via Travis, but to avoid potential fees we should migrate it over to GitHub Actions. This should be almost as straightforward as copying across the relevant configuration from a currently set-up repo (see e.g. pyrolite workflows).