github.event.workflow_run.conclusion is always null #58929
Replies: 1 comment
-
🕒 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.
-
Select Topic Area
Question
Body
I am using github.event.workflow_run.conclusion in conjunction with worflow_run:
However, github.event.workflow_run.conclusion is always returning null, and both passing and failing cases are skipped.
I found an old discussion about a similar issue. They used octokit/request-action as a workaround, but that is not working for me.
Additionally, workflow_run (id, name, conclusion) attributes seem to be empty or null.
Why github.event.workflow_run attributes (id, name, conclusion) are empty?
Any new workarounds?
Beta Was this translation helpful? Give feedback.
All reactions