flatpak-external-data-checker
flatpak-external-data-checker copied to clipboard
flathub-infra
Support `beta` and `branch/*` branches
Use case :
JetBrains have what they call the EAP (Early Access Program) for their products. It's kinda like a public beta for upcoming versions of their products. The release process of the EAP versions is separated from the main release one.
I would like to be able to bundle these EAP versions into flathub, either in the beta or branch/eap branch. Would be nice if the data checker could check for updates in both master and the other flathub supported branches.
Sounds great! @barthalion how do you think would be best to arrange for the tool to be run on additional branches for some repos? I think that'd be the only change needed here.
It would need to iterate over master, beta and all branch/* branches. That's why I was initially using pygit2 for detecting default branch before botching it.
I have also some users that stay on the beta branch and currently I have to do everything manually for the beta branch and everything happens automatically for the stable branch.
While this feature is surely something we'd like to have, it's not trivial to implement in a reliable way.
@sophie-h In the Telegram flatpak repo, the default branch is beta and all the updates (including pre-releases) land there. Once a stable version is released, we manually merge beta to master. Maybe similar workflow would work for you in the meantime?
I think I will stick with --edit-only for now (which already helps a lot.) But thanks for the suggestion!
For extensions where multiple branch/* are maintained at the same time (e.g. org.freedesktop.Sdk.Extension.mono6), this is useful as well!
This is only a limitation with flathub's instance of f-e-d-c. You can avoid this problem and check arbitrary branches by using the custom workflow as described in the readme.
Does this suggest something that is similar to snap's --channel=latest/<channel> (default --channel=latest/stable and --channel=latest/beta, etcetera; and custom branches: --channel=esr/stable?
