feat(docker): extend CI to push images to Forgejo

Enhanced the CI pipeline for Docker images by supporting an additional push to the Forgejo Docker Registry alongside the existing push to Docker Hub. This change allows for better integration with private infrastructures and provides an alternative for users and systems that prefer or require images to be stored in a more controlled or private registry. It involves logging into both Docker Hub and Forgejo with respective credentials and pushing the built images to both, ensuring broader availability and redundancy of our Docker images.

.forgejo/workflows/docker-latest.yml

@@ -24,8 +24,19 @@ jobs:
         with:
           username: ${{ secrets.DOCKERHUB_USERNAME }}
           password: ${{ secrets.DOCKERHUB_TOKEN }}
-      - name: Build and push
+      - name: Build and push to Docker Hub
         uses: docker/build-push-action@v5
         with:
           push: true
           tags: kumitterer/matrix-gptbot:latest
+      - name: Log in to Forgejo Docker Registry
+        uses: docker/login-action@v3
+        with:
+          registry: git.private.coffee
+          username: ${{ secrets.GITHUB_ACTOR }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+      - name: Build and push to Forgejo Docker Registry
+        uses: docker/build-push-action@v5
+        with:
+          push: true
+          tags: git.private.coffee/privatecoffee/matrix-gptbot:latest