inconsistent usage of the term "cancelled"/"canceled" #145209
Replies: 1 comment
-
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
The term "cancelled"/"canceled" is used in an inconsistent manner within GitHub Actions. This could lead to confusion for users.
For example: The REST-api uses the term cancelled to indicate that a workflow was cancelled by the user (source). However, the error message underneath the workflow run spells cancelled with just one L.
This might cause confusion when users want to create an if-statenent within a job like
${{ always() && contains(needs.*.result, 'canceled')) }}
as the term "canceled" is not recognised by the REST-api.Beta Was this translation helpful? Give feedback.
All reactions