Integrating Flathub releases with my release pipeline

Hi,

I did set up auto merge for flathub-beta a while ago

github.com/flathub/io.mrarm.mcpelauncher

.github/workflows/merge-nightly.yml

master

name: Merge Nightly

on:
  workflow_dispatch:
    inputs:
      pr-number:
        type: string
  issue_comment:
    types:
      - created

run-name: ${{ ((github.actor_id == '45397632' || github.actor_id == 45397632) && github.event.issue.pull_request != null && contains(github.event.issue.labels.*.name, 'beta-update') && contains(github.event.comment.body, 'flatpak install') || inputs.pr-number) && format('Auto Merge PR {0}', github.event.issue.number || inputs.pr-number) || 'Ignore Comment - Skip Automerge' }}

jobs:
  check-comment:
    if: (github.actor_id == '45397632' || github.actor_id == 45397632) && github.event.issue.pull_request != null && contains(github.event.issue.labels.*.name, 'beta-update') && contains(github.event.comment.body, 'flatpak install') || inputs.pr-number
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Perform action for "flatpak install" comment

This file has been truncated. show original

E.g.

• I added a special label beta-update to the pr as a filter so only specific PRs get auto merged
• Take care to not auto merge PRs from untrusted forks/users
• Usually users from forks cannot freely decide about pr labels
• This workflow checks the author of the done comment is done by flathub bots account id not anyone trying to fake that entity
• The flathub bot comment is usually some minutes after the commit status, but good enough for full automation

I cannot say if this is good solution, but merging possible daily beta PRs by hand is not manageable.