💡 Improve visibility of workflow_dispatch inputs in run details

[enXov]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Actions Runner

Discussion Details

💡 Feature Request: Improve workflow_dispatch Input Visibility & Add Pre-Execution Review

Hi GitHub Team,

I’d like to suggest one related UX improvements for GitHub Actions workflow_dispatch workflows.

---

1. Problem: Limited visibility of workflow inputs during execution

When triggering a workflow manually using workflow_dispatch, the input values are not consistently visible in a clear and persistent way during or after execution.

In practice, this makes it difficult to:

• Quickly verify what inputs were used for a running workflow

Although the workflow run page shows logs and summary information, the actual input parameters are not always easy to find in a dedicated section.

---

2. Proposed improvement: Input visibility panel in run details

Add a dedicated “Inputs” panel in the workflow run details page (for workflow_dispatch runs), ideally under or alongside the “Workflow file” section.

This panel should:

• Clearly display all input parameters used for the run
• Be visible during execution and after completion
• Provide a single source of truth for debugging and validation

---

Why this matters

• Improves transparency of CI/CD executions
• Reduces debugging time for failed workflows
• Prevents wasted compute resources from incorrect inputs
• Improves confidence when triggering manual workflows
• Enhances overall GitHub Actions UX consistency

---

Extra note

This is especially important for production deployments and long-running CI pipelines where incorrect inputs can cause significant time and resource waste. People can make mistakes espicially on the workflow_dispatch.

Thanks!

[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. ⭐