workflow: Auto-create PRs on releases

[Venefilyn]

Should automatically create PRs whenever Cockpit clients update. This
runs every 10 minutes

Signed-off-by: Freya Gustavsson freya@venefilyn.se

[flathubbot]

🚧 Test build enqueued.

[flathubbot]

🚧 Started test build.

[Venefilyn]

@bbhtt just wanted to check if this would work. In short want to replicate the results of #64 but automated. Currently we run this workflow but since it's in our org we can't create a PR to here https://github.com/cockpit-project/cockpit/actions/runs/16777815636/job/47508259219

[flathubbot]

✅ Test build succeeded. To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/202395/org.cockpit_project.CockpitClient.flatpakref

[bbhtt]

Either is fine, this x-checker config will be picked up by a global x-checker action that runs for every repo on Flathub org. It runs daily at intervals of 4–6 hours.

You can also configure a workflow to send PRs with updates from upstream repo to here so that whenever you push a tag/release a PR is more or less immediately opened here.

[Venefilyn]

You can also configure a workflow to send PRs with updates from upstream repo to here so that whenever you push a tag/release a PR is more or less immediately opened here.

@bbhtt we tried that but running into permission issues and we presumed it wasn't possible. You mean having a workflow in this repo? Any examples you have for it?

[bbhtt]

You have to use a token which has access to both here and upstream like your personal token.

eg. is https://github.com/FreeTubeApp/FreeTube/blob/development/.github/workflows/flatpak.yml but not much to tell from there, the token part is not visible.

[flathubbot]

🚧 Test build enqueued.

[flathubbot]

🚧 Started test build.

[flathubbot]

✅ Test build succeeded. To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/252864/org.cockpit_project.CockpitClient.flatpakref

Built for aarch64 and x86_64 architectures.

⚠️ Linter warnings:

Warnings can be promoted to errors in the future. Please try to resolve them.

• 'appstream-missing-vcs-browser-url' warning found in linter repo check. Details: Please consider adding a vcs-browser URL to the Metainfo file