chore(mirror): remove force_workspace reusable + smoke (R4 mothballed)#144
Conversation
R4 force_workspace is obsolete: Mergify's ignore_conflicts:true config already creates the backport workspace PR, resolves toward theirs, and applies backport-conflict for path-drift conflicts (canary-verified on VyOS-Networks/ipaddrcheck#26/#27). The reusable's 'No backport have been created' trigger never fires under that config. Source wrappers already removed across the 13 consumers; consumers.yaml schema removal follows. T8943 / IS-510.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughSummary by CodeRabbit
WalkthroughDeleted two GitHub Actions workflows: Changes
Possibly related PRs
✨ Finishing Touches✨ Simplify code
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. Comment |
R4 force_workspace is obsolete. The Rollout 4 canary proved Mergify's
ignore_conflicts: trueconfig already creates the backport workspace PR, resolves toward theirs, and appliesbackport-conflictfor path-drift conflicts (deleted-by-us verified on VyOS-Networks/ipaddrcheck#27). The reusable'sNo backport have been createdtrigger never fires under that config.Removes the reusable + its smoke test. Source wrappers already removed across all 13 consumers; consumers.yaml schema removal follows. Pure deletion; Phase 0 clean; adversarial skip-eligible. T8943 / IS-510.
🤖 Generated by robots