F-Droid runner causing failure
The default Docker images on the F-Droid runner that's still enabled doesn't appear to be Debian-based, causing some CI jobs that don't specify an image (and wish to use the runner's default) (example) to fail. I'm wondering now that we have a few of our own runners in production, and can easily deploy new ones in Puppet, if we should even keep the F-Droid ones around? Or at least maybe make them refrain from accepting untagged jobs?