flathub / actions

Internal GitHub Actions

Flathub

Flathub is the central place for building and hosting Flatpak builds.

Using the Flathub repository

To install applications that are hosted on Flathub, use the following:

flatpak remote-add flathub https://flathub.org/repo/flathub.flatpakrepo
flatpak install flathub org.gnome.Recipes

To install applications from the beta branch, use the following:

flatpak remote-add flathub-beta https://flathub.org/beta-repo/flathub-beta.flatpakrepo
flatpak install flathub-beta org.godotengine.Godot

For more information and more applications see https://flathub.org

Contributing to Flathub

For information on creating packages or reporting issues please see the contributing page.

Note: this repository is not for reporting issues related to the flathub.org website itself or contributing to its development. For that, go to https://github.com/flathub-infra/website

actions's Issues

Appdata xml validation at start of building to avoid wasting build time

Note: If this is not the appropiate issue tracker for this issue then please let me know.

When submitting or updating an app, it's not uncommon to have your build only failed by appdata xml validation (like this).

I think much infra build time could be preserved by performing appdata xml validation as a first step (as well as keeping it in last steps).

In my particular case when upgrading an app, both aarch64 and x86_64 builds took a long time just to fail at the end because there was a link in the description for the new release and that failed the appdata validation. I'm not complaining for my time but for the build server resources wasted.

External data checker folder is unclear

While trying to write a readme for #12 I came accross the folder https://github.com/flathub/actions/tree/master/flathub-external-data-checker and could not figure out how those files are used. Are they pulled to a server? Are they run in a certain interval? Are they old and should be removed?

Add a readme, that clarifies what this is for

Hey,

I'm wondering if this is an action third party packages could use to package for flathub. Read the code, but no to sure why and what is happening.

Clone the repo recusively

Currently, the merge action fails to merge JSON manifests that uses shared-modules as flatpak-builder just fails to show the manifest.

Needed for flathub flathub/flathub#1270

Merge action fails on multiple valid manifests

If there are more than one valid manifests in a single git repo, the action assumes the last one found to be the only manifest.
This can result in the action to fail like in flathub/flathub#1953 (comment)