Feature Request: Auto-redirect to workflow run details after manual dispatch

[enXov]

Why are you starting this discussion?

Product Feedback

What GitHub Actions topic or product is this about?

General

Discussion Details

Hi GitHub Team,

I've been following the "What’s coming in early 2026" roadmap and was excited to see the plan for "Returning the run ID from workflow dispatch".

Building on this upcoming technical improvement, I'd like to suggest a UI/UX enhancement for the GitHub Actions dashboard.

The Problem

Currently, when a user manually triggers a workflow via the "Run workflow" button, they remain on the workflow list page. To monitor the progress, the user has to:

1. Wait for the list to refresh (or manually refresh).
2. Find the new run in the list.
3. Click on it to see the logs.

Proposed Solution

Immediately after clicking "Run workflow", the UI should use the newly generated Run ID to automatically redirect the user to that specific workflow run's details/logs page.

Why this is a priority for 2026:

1. Perfect Synergy: Since you are already working on returning the Run ID from dispatch, this is the most logical next step for the Web UI.
2. Immediate Feedback: Developers almost always want to see the live logs right after triggering a manual run (e.g., for deployments or manual tests).
3. Reduced Friction: It eliminates unnecessary clicks and page refreshes, making the "manual trigger" flow feel much more modern and responsive.

I've searched for similar discussions, and while many mention general UI speed, this specific "auto-redirect" flow would be a game-changer for daily productivity.

Would love to hear the team's thoughts on incorporating this into the 2026 UX roadmap!

Best regards.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐