Repository navigation
ci: finish migrating Platform automation - #5158
Conversation
@coderabbitai full review |
✅ Action performedFull review finished. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📜 Recent review details
📝 Walkthrough
Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to
|
Evaluated exact head
The release, task-scanning and updater configurations activate on their normal post-merge events. Their post-merge execution remains part of #5157; this pre-merge CI result is not a claim that those future runs have already happened. |
Why
Platform still relies on the legacy Actions repository for four routine automations. Those dependencies must move before that repository can be deleted.
What
Move CI aggregation, releases, task scanning and skill updates to the reviewed maintained catalogue. Preserve their existing inputs, permissions and failure handling.
Part of #5157