{
"$type": "site.standard.document",
"bskyPostRef": {
"cid": "bafyreigtyrct374xs4x33kpltguv74fuylu6kulqiggnjtpxz7nflhos6e",
"uri": "at://did:plc:yrn4rbgwenb6lfhhzjegbtnc/app.bsky.feed.post/3mjatytuxzus2"
},
"path": "/t/integrating-flathub-releases-with-my-release-pipeline/11973#post_2",
"publishedAt": "2026-04-11T11:41:44.000Z",
"site": "https://discourse.flathub.org",
"tags": [
"github.com/flathub/io.mrarm.mcpelauncher",
".github/workflows/merge-nightly.yml",
"master",
"show original"
],
"textContent": "Hi,\n\nI did set up auto merge for flathub-beta a while ago\n\ngithub.com/flathub/io.mrarm.mcpelauncher\n\n#### .github/workflows/merge-nightly.yml\n\nmaster\n\n\n name: Merge Nightly\n\n on:\n workflow_dispatch:\n inputs:\n pr-number:\n type: string\n issue_comment:\n types:\n - created\n\n 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' }}\n\n jobs:\n check-comment:\n 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\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v4\n - name: Perform action for \"flatpak install\" comment\n\n\nThis file has been truncated. show original\n\nE.g.\n\n * I added a special label `beta-update` to the pr as a filter so only specific PRs get auto merged\n * Take care to not auto merge PRs from untrusted forks/users\n * Usually users from forks cannot freely decide about pr labels\n * This workflow checks the author of the done comment is done by flathub bots account id not anyone trying to fake that entity\n * The flathub bot comment is usually some minutes after the commit status, but good enough for full automation\n\n\n\n* * *\n\nI cannot say if this is good solution, but merging possible daily beta PRs by hand is not manageable.",
"title": "Integrating Flathub releases with my release pipeline"
}