Update README

.github/workflows/build_image.yml

@@ -6,7 +6,7 @@ on:
 jobs:
   build:
     runs-on: ubuntu-20.04
-    name: Clone telegram api server repo
+    name: Build amd64 and arm64 images
     steps:
       - name: Checkout API repo
         uses: actions/checkout@v2
@@ -30,7 +30,15 @@ jobs:
         uses: docker/setup-qemu-action@v1
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v1
-      - name: Build Docker image
+      - name: Login to GHCR
+        if: github.event_name != 'pull_request'
+        uses: docker/login-action@v1
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GCHR_PAT }}
+      - name: Prepare for push
+        id: prep
         run: |
           DOCKER_IMAGE=ghcr.io/${{ github.repository_owner }}/tdlib-telegram-bot-api-docker/telegram-api-server
           VERSION=edge

README.md

@@ -13,11 +13,13 @@ This project does not modify any part of the [tdlib/telegram-bot-api](https://gi
 ## Issues
 
 As I do not modify any part of the server code I am not responsible for the way it works. For that purpose you should open an issue on the [telegram bot api server](https://github.com/tdlib/telegram-bot-api/issues) issue tracker.
+
 **TL;DR:** My responsibility ends when container and binary starts.
 
 ## Build schedule
 Build will be triggered automatically once a week to produce the latest version of the Telegram API Server.
-I would set it for the daily release but every build takes ~25 minutes and generates additional costs on my side.
+I would set it for the daily release but every build takes ~2.5 hours and generates additional costs on my side.
+
 Images are versioned in format `1.0.x` where `x` is a build number.
 
 ## How to use the image