Inform about flatpak/flatpak-github-actions in README.md

[PhrozenByte]

First of all: Thank you for your amazing project and sharing it with the world! ❤️ It really made my day: I'm rather new to Flatpak and it solved many headaches I had about managing a local Flatpak repo and notably with flatpak-builder practically not supporting --system --install and flatpak build-bundle not supporting extra data.

I was wondering, what is the difference between Flatter and flatpak/flatpak-github-actions mentioned at the end of Flatter's README.md? Is it just that flatpak/flatpak-github-actions won't create a .flatpakrepo file and that Flatter makes it easier to upload the repo to GitHub pages? I was a little confused about what to use, because they seem to be very similar. Thus it might be a good idea to inform users about the differences in Flatter's README.md.

Besides, flatpak/flatpak-github-actions also provides some more and especially more up-to-date runtimes (see https://github.com/flatpak/flatpak-github-actions?tab=readme-ov-file#docker-image). Since they work as well, Flatter might simply link them and concentrate on providing different runtimes.

[andyholmes]

Hi,

As the README explains, Flatter is intended to build and host a project in GitHub pages, specifically for low-traffic nightly/development builds.

flatpak-github-actions doesn't have a strict definition AFAIK, it's just a collection of Flatpak CI tools for GitHub. Flatter started as a fork of flatpak-github-actions, but it's primary use case is for me to build, test and distribute nightlies for my projects.

I'm happy to accept patches, but I don't really have any intention of competing with flatpak-github-actions. I sort of just update the runtimes I use and sometimes add things when folks ask, so it's really up to you which is a better fit 🙂

[PhrozenByte]

I didn't want to leave the impression that Flatter is competing with flatpak-github-actions - as you said, Flatter is doing something else. I just wanted to note that, as a beginner, the documentation didn't make it clear to me at first that they do different things. I do know it now. This could be made more clear by explicitly mentioning flatpak-github-actions as alternative if one doesn't actually want to host a Flatpak repo, but to publish to an existing Flatpak repo like Flathub - if that's even true, I'm not entirely sure 😆

For me personally Flatter is a perfect match. Not even for some software project of my own, but to build a Flatpak slightly different from what is on Flathub.

Considering the Docker images of flatpak-github-actions: I believe that it could be mentioned in the README.md that they are a thing. Besides, thank you for upgrading your runtimes 👍

Again, big thank you for your project! ❤️