From b76518a1b7a27c538ce64f85a1266de53362191d Mon Sep 17 00:00:00 2001 From: Yuriy Andamasov Date: Tue, 2 Jun 2026 03:38:06 +0300 Subject: [PATCH] chore(mirror): remove force_workspace backport wrapper (R4 mothballed) Mergify ignore_conflicts:true already creates the backport workspace PR + resolves toward theirs + applies backport-conflict for path-drift conflicts (verified by canary VyOS-Networks/ipaddrcheck#26/#27). force_workspace's 'No backport have been created' trigger never fires under that config. T8943 / IS-510. --- .../workflows/force-workspace-backport.yml | 25 ------------------- 1 file changed, 25 deletions(-) delete mode 100644 .github/workflows/force-workspace-backport.yml diff --git a/.github/workflows/force-workspace-backport.yml b/.github/workflows/force-workspace-backport.yml deleted file mode 100644 index 37fba9f..0000000 --- a/.github/workflows/force-workspace-backport.yml +++ /dev/null @@ -1,25 +0,0 @@ -# .github/workflows/force-workspace-backport.yml -# DO NOT EDIT — managed by mirror-pipeline Rollout 4. -name: force_workspace backport companion - -on: - issue_comment: - types: [created] - -permissions: - contents: read - -jobs: - call: - # No-op on the public source (owner != VyOS-Networks); active on the mirrored target copy. - if: | - github.repository_owner == 'VyOS-Networks' - && github.event.issue.pull_request != null - && github.event.comment.user.login == 'mergify[bot]' - && contains(github.event.comment.body, 'No backport have been created') - uses: vyos/.github/.github/workflows/force-workspace-backport.yml@production - with: - mergify_comment_id: ${{ github.event.comment.id }} - mergify_comment_body: ${{ github.event.comment.body }} - target_pr_number: ${{ github.event.issue.number }} - secrets: inherit