[nickvergessen]

How

• The bot shallow-clones nextcloud/.github once. For each branch it already translates, after the translations commit, it runs the same logic as sync-workflow-templates.yml:
• It only touches workflows the app already has.
• It compares md5 hashes against .github/actions-lock.txt and creates that file if it's missing.
• It reapplies any *.yml.patch files.
• It skips the sync while a merge freeze is active (when the app has block-merge-freeze.yml).

What

• Nothing changed: the translations are pushed, as before.
• Patches applied cleanly: a second commit, ci(actions): Update workflow templates…, goes onto the branch and both commits are
  pushed together.
• A patch failed: the translations are pushed to the branch. The workflow commit is force-pushed to
  automated/noid/-update-workflows, which is the branch name the action uses, so if the action is still enabled in an app
  both end up on the same PR. A draft PR is then opened through the API with the same title and checklist as the action.

Where

• Mechanism is Opt-In for apps: .github/actions-lock.txt is the opt-in
• Limited to nextcloud org
• Temporary limited to nextcloud/spreed repo to test it

Why

• Currently the workflow creates PRs
• The PRs can not be automerged as that is not allowed for PRs touching workflow files
• Currently spams 5 notifications per maintained branch per app, for me it was 5*34 => 170 this weekend

Note

Yes it's abuse to do this on translation sync, but we already loop over all repositories here and cloned them already, so it's the best starting point

🤖 AI (if applicable)

• The content of this PR was partly or fully generated using AI (N/A)