Skip to content

chore(mirror): remove force_workspace backport wrapper (R4 mothballed)#22

Merged
andamasov merged 1 commit into
rollingfrom
chore/mothball-force-workspace-wrapper
Jun 2, 2026
Merged

chore(mirror): remove force_workspace backport wrapper (R4 mothballed)#22
andamasov merged 1 commit into
rollingfrom
chore/mothball-force-workspace-wrapper

Conversation

@andamasov

Copy link
Copy Markdown
Member

Removes the inert force_workspace backport companion wrapper. R4 mothballed: Mergify's ignore_conflicts: true already provides the conflict-backport workspace + theirs-resolution + backport-conflict label for path-drift conflicts (canary-verified). Pure deletion; Phase 0 clean on representative (vyos/ipaddrcheck); adversarial skip-eligible (byte-identical deletion). T8943 / IS-510.

🤖 Generated by robots

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.
@andamasov andamasov merged commit 779cfe1 into rolling Jun 2, 2026
1 check was pending
@coderabbitai

coderabbitai Bot commented Jun 2, 2026

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 3ad69423-78a6-4643-8043-46217dbac31b

📥 Commits

Reviewing files that changed from the base of the PR and between 6307fe8 and b76518a.

📒 Files selected for processing (1)
  • .github/workflows/force-workspace-backport.yml

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Removed automated backport workflow configuration.

Walkthrough

This PR removes .github/workflows/force-workspace-backport.yml, a 25-line GitHub Actions workflow that triggered backport automation. The workflow listened for Mergify bot comments containing "No backport have been created" and invoked a reusable backport workflow from the VyOS organization.

Changes

Cohort / File(s) Summary
Workflow Configuration
.github/workflows/force-workspace-backport.yml
Deleted GitHub Actions workflow that automatically triggered backports based on Mergify bot comments.

Possibly related PRs

  • vyos/vyatta-biosdevname#21: Adds the force-workspace-backport workflow that this PR deletes; directly inverse operation at the same file level.
✨ Finishing Touches
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch chore/mothball-force-workspace-wrapper

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@mergify mergify Bot added the rolling label Jun 2, 2026
@vyos-bot vyos-bot Bot added mirror-initiated This PR initiated for mirror sync workflow mirror-completed This PR has been mirrored successfully and removed mirror-initiated This PR initiated for mirror sync workflow labels Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mirror-completed This PR has been mirrored successfully rolling

Development

Successfully merging this pull request may close these issues.

1 participant