Update README, add schedule

Author: lzap

.github/workflows/fedora.yml

@@ -1,8 +1,3 @@
-# Build Fedora 43 bootc container images for multiple clouds and architectures.
-# Runs 8 build jobs in parallel (4 containerfiles × 2 arches) on native runners,
-# then a single manifest job to publish multi-arch images. Uses ghcr.io as
-# a shared registry cache across all jobs.
-
 name: Build Fedora
 
 on:
@@ -11,6 +6,8 @@ on:
   pull_request:
     branches: [main]
   workflow_dispatch:
+  schedule:
+    - cron: '13 4 * * *'
 
 permissions:
   contents: read

.gitignore

@@ -1,2 +1 @@
 /generator/generator
-/*.local.sh

README.md

@@ -1,20 +1,34 @@
 # Derived bootc images for image builder
 
-This repository contains `Containerfile`s with necessary changes for base
-containers in order to build various image types like cloud or installer.
+This repository contains `Containerfile` for each derived image types that
+are used by image builder.
+
+## Supported image formats
+
+* AWC EC2
+* Azure
+* GCE
+* qcow2
+
+## Supported bootable containers
+
+* `quay.io/fedora/fedora-bootc` (x86_64, aarch64)
 
 ## Building Containerfiles
 
-Use `make` to build Containerfiles from templates.
+Use `make` to build Containerfiles from templates. Go is required in order to
+build a small templating command that processes the templates.
 
 ## Building container images
 
-Use `./build.sh` to build and push container images.
+Push the changes into this repository, GitHub Actions will build and publish new
+versions of container images. Daily rebuild is scheduled for every morning
+(CET).
+
+* Fedora 43: [![Fedora](https://quay.io/repository/osbuild/fedora-bootc/status "Fedora")](https://quay.io/repository/osbuild/fedora-bootc)
 
 ## TODO
 
-* Supported OSes: Fedora N, N-1, Stream 9/10, RHEL latest (10.2/9.8)
+* Supported OSes: Fedora N, N-1, Stream 9/10, RHEL latest (10.2/9.8 downstream only)
 * Use `--from` to have less Containefiles (not too much useful at this point)
 * Figure out a good comment for all Containerfile explaining to end users what to do
-* Write GHA action with caching support for container storage
-* Use GHA matrix to distribute the build across many nodes