Deployment timestamp is misleading for approval-gated deployments

[TAK-TomasBartalos]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

When a deployment requires environment approval, the Deployments page appears to display the time when the deployment was queued/requested, not when it was actually executed or completed.

Example
Deployment requested: 2 days ago
Deployment approved: 11 minutes ago
Deployment executed successfully: 11 minutes ago

The Deployments page shows:
Success .... 2 days ago

while the workflow logs show that the deployment actually ran 11 minutes ago.

Expected behavior

The deployment timestamp should reflect when the deployment was executed or completed, or the UI should display separate timestamps such as:

Requested at
Executed at

Why this matters

For deployments requiring manual approval, the queue time can differ significantly from the actual production release time. Users typically want to know when the new version reached the target environment, not when the deployment request was initially created.
This creates confusion during release tracking, as a result teams can be misled about when a release actually hit the production.

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