Merge pull request #104 from pi-hole/bye-bye-bye

We don't need these anymore

Author: PromoFaux

.github/workflows/docker-pi-hole-base.yml

@@ -20,19 +20,3 @@ All images are pushed to both Docker Hub (`pihole/ftl-build`) and GHCR (`ghcr.io
   - Every `workflow_dispatch` event triggers a build of the branch it is run against, and uploads a branch-based tag
   - Every `tag` event (e.g `v1`) triggers a build and uploads both `${{matrix.ARCH}}` and `v1-${{matrix.ARCH}}` tags
   - Schedule: 1:30am UTC every Sunday a build is triggered and a `${{matrix.ARCH}}` tag is uploaded
-
-# Docker Pi-hole Base Images [![Docker Pulls](https://img.shields.io/docker/pulls/pihole/docker-pi-hole-base)](https://hub.docker.com/r/pihole/docker-pi-hole-base) [![Image Builds](https://github.com/pi-hole/docker-base-images/actions/workflows/docker-pi-hole-base.yml/badge.svg)](https://github.com/pi-hole/docker-base-images/actions/workflows/docker-pi-hole-base.yml)
-
-All the images used by the pihole/docker-pi-hole repo to build the contents of that repo
-
-Tag Patterns:
- - Multiarch Debian Version tags, such as `buster-slim` and `bullseye-slim`. These are always the latest builds for the given debian version
-
-All images are pushed to both Docker Hub (`pihole/docker-pi-hole-base`) and GHCR (`ghcr.io/pi-hole/docker-pi-hole-base`)
-
-## How does it get uploaded?
-
-- GitHub Actions (`docker-pi-hole-base.yml`):
-  - Every `pull_request` event triggers a build (but does not push)
-  - Every `workflow_dispatch` event triggers a build of the branch it is run against, and uploads a branch-based tag
-  - Schedule: 1:30am UTC every Sunday a build is triggered and a `${{matrix.ARCH}}` tag is uploaded