Native CI Orchestration: Trigger and Re-run Tests Directly from the Currents Dashboard

The Problem: The "Context-Switching" Friction Currently, our testing workflow is fragmented across two platforms. To initiate or re-run a test suite, we must navigate to GitHub Actions; to analyze the results, we must then switch over to Currents.dev. This back-and-forth creates unnecessary friction, slows down the debugging cycle, and forces developers to manage two different interfaces for a single task.

The Proposal: A Unified Execution & Observation Hub We would like to propose the ability to trigger and manage test runs directly from within the Currents.dev UI. Instead of Currents being a passive destination for results, it would become an active orchestration hub. This functionality would allow teams to:

• Launch New Runs: Trigger specific GitHub Action workflows (via repository dispatch or similar integration) directly from the Currents dashboard.

• Smart Re-runs: Re-execute failed tests or entire flakes with a single click inside the Currents run view, rather than hunting for the specific job in CI.

• Centralized Control: View real-time logs and execution progress without ever leaving the Currents ecosystem.

Why this is a Game-Changer:

1. Velocity: Dramatically reduces the "Mean Time to Repair" (MTTR) by allowing developers to re-run failed tests the moment they identify them in the dashboard.

2. Simplified DX (Developer Experience): Provides a "Single Pane of Glass" for the entire testing lifecycle—from execution to post-mortem analysis.

3. Competitive Alignment: Similar orchestration capabilities are highly valued in other dashboard environments (like Cypress Cloud), and bringing this to Currents would solidify its position as the premier choice for scalable test management.

By bridging the gap between CI execution and Currents reporting, you would be providing a seamless, world-class workflow that saves time for every engineer on the team.