Provide a cancellation reason in the "needs" context

[chuanwu-aderant]

Why are you starting this discussion?

Product Feedback

What GitHub Actions topic or product is this about?

General

Discussion Details

Could we add a cancellation_reason property to the needs context?

We currently have a workflow with 2 jobs (Job A and Job B), where Job B only runs if Job A fails. This conditional run is achieved through the needs context.

We want to consider some of the cancellation reasons as a failure for Job A, however, there is no way to find out why Job A was cancelled.

If Job A gets cancelled due to a timeout we would like Job B to run. If Job A was cancelled due to workflow concurrency settings or manually cancelled, then these are valid cancellation reasons and so Job B should not run.

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