Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Determining result of Workflow Dispatch
See original GitHub issueUnable to identify the cause of failure for workflow dispatch event
As we known, dispatch doesn’t return anything, making it extremely difficult to identify the cause of failure for a workflow trigger.
As an example, assume a workflow requires a specific input which is not provided in the call - the method has no way of providing us with such information on failure.
Do we have a way to identify at minimum the status code returned from the dispatch?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Workflow syntax for GitHub Actions
A workflow is a configurable automated process made up of one or more jobs. You must create a YAML file to define your...
Read more >GitHub Actions: How to view inputs for workflow_dispatch?
This will result in output you can view in your GitHub action execution output with the inputs serialized as JSON:
Read more >GitHub Actions On Demand | Blog - Ardalis
You just go to the actions tab, choose the workflow, and you should see an option to "Run workflow".
Read more >GitHub Actions: Manual triggers with workflow_dispatch
Workflow dispatch inputs are specified with the same format as action inputs. The triggered workflow receives the inputs in the github. event ...
Read more >Defining Field Service Workflow - ServiceNow Docs
The Field Service workflow configuration can streamline the way that ... Identify crews and agents for crew tasks on Dispatcher Workspace.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
PR is here: https://github.com/hub4j/github-api/pull/1455 .
I don’t know what I was thinking when I implemented it…
Will a new release of the API come out soon with this fix?