coverage: 91.339%. remained the same when pulling 4566e24 on afuetterer:github-actions into ee4d7ff on rdmorganiser:master.

thanks @afuetterer , I agree to make this into a PR and have just one question.

In #586, I wrote for the on: push: condition to include tags and release/**. However, at the moment we don't have any special pipeline for tags or release so this is actually not needed right?

on: 
  push:
    branches: 
      - master
      - 'releases/**'
    tags:
      - '*.*.*'
  pull_request:

Hi @MyPyDavid, I just wanted to speed things up a bit and a more atomic change to be merged quickly. #586 is important, but also a very big change, that could take longer. The PR was opened in February. 😄

Yes, sure, if you want to include tags and releases to trigger the CI, please include those.

But what you suggest means that a branch's name has to start with "releases". To trigger CI on a release, like you did with tag, is actually:

on: 
  push:
    release:
      types: [published]
...

see: https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#release

And yes, you could trigger a CI run to push a package to PyPI or build documentation or something.

Feel free to edit my commit.