(MOT-4367) feat(ci): expose manual test pipelines - #725
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughSix E2E workflows now accept execution metadata, use it for run names and concurrency groups, and optionally check out a specified source SHA. ChangesE2E workflow identity
Estimated code review effort: 3 (Moderate) | ~20 minutes Suggested reviewers: Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
skill-check — worker0 verified, 54 skipped (no docs/).
Four for four. Nicely done. |
What changed
Why
Release Control needs a safe, allowlisted way to dispatch tests without exposing release or promotion workflows and without correlating runs by timing.
Impact
Existing pull request, scheduled, and reusable workflow behavior remains unchanged. Manual executions can now be tracked deterministically by Release Control.
Validation
actionlinton all six changed workflowsgit diff --checkRefs MOT-4367
Summary by CodeRabbit