Explanation for GitHub Workflow run statuses #70540
-
Select Topic AreaQuestion BodyThe GitHub API for workflow runs allows a
|
Beta Was this translation helpful? Give feedback.
Replies: 14 comments 1 reply
-
|
I'd like to know the lifecycle for the states as well. The official docs just mention the states without specifying what they signify. For e.g. what's the difference between requested, waiting, pending and queued? |
Beta Was this translation helpful? Give feedback.
-
|
Please Github. Your API has a great, methodic and exhaustive list of all its endpoints with json schemas, but it's missing the meanings behind values like these. |
Beta Was this translation helpful? Give feedback.
-
|
+1 I'm trying to query all active workflows for a given repository and understanding the meanings of these statuses would help in making my logic more robust. |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
|
bump |
Beta Was this translation helpful? Give feedback.
-
|
+1 I have workflows which are stuck in the pending status and I can't find them on the Github Actions Tab as there is no filter for |
Beta Was this translation helpful? Give feedback.
-
|
in particular i would like to know:
i would suggest to place a state diagram in the docs |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
|
SO... dose anyone know this from trial and error? |
Beta Was this translation helpful? Give feedback.
-
|
+1 especially the |
Beta Was this translation helpful? Give feedback.
-
|
I am currently developing an app that integrates with GitHub Workflows. In my use case, I have a In this context, the |
Beta Was this translation helpful? Give feedback.
-
|
It is now documented in Check statuses and conclusions Checks can have many different statuses. Statuses describe the state of a check from when it is created to when it is completed. Some statuses cannot be set manually and are reserved for GitHub Actions. When a check has a status of completed, it has a conclusion. The conclusion describes the result of the check. All possible check statuses and conclusions are described in the link above. |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.


It is now documented in Check statuses and conclusions
Checks can have many different statuses. Statuses describe the state of a check from when it is created to when it is completed. Some statuses cannot be set manually and are reserved for GitHub Actions. When a check has a status of completed, it has a conclusion. The conclusion describes the result of the check. All possible check statuses and conclusions are described in the link above.