summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYuriy Andamasov <yuriy@andamasov.com>2026-06-02 03:37:28 +0300
committerGitHub <noreply@github.com>2026-06-02 03:37:28 +0300
commit638f105c50d232b65b780b74cb67be0265f70e88 (patch)
treed344cc0f8b42b704608a6959293bc26662bc4326
parentb336d0d4be07639cc7b56e3e059d0de67d03e127 (diff)
downloadipaddrcheck-638f105c50d232b65b780b74cb67be0265f70e88.tar.gz
ipaddrcheck-638f105c50d232b65b780b74cb67be0265f70e88.zip
chore(mirror): remove force_workspace backport wrapper (R4 mothballed) (#41)
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.
-rw-r--r--.github/workflows/force-workspace-backport.yml25
1 files changed, 0 insertions, 25 deletions
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