I was interested by the point you raised about multiple parameters status: queued, in_progress This was indeed something I had issues with, being the UK, starting a job now almost immediately triggers and goes straight to in in_progress but later in the day may be queued. Running curl -i -H "Authorization: token <my_token>" https://api.github.com/repos/colinbruce/<my_repo>/actions/runs?status=in_progress correctly returns 0 jobs however, running curl -i -H "Authorization: token <my_token>" https://api.github.com/repos/colinbruce/<my_repo>/actions/runs?status=in_progress,queued returns all jobs on the repo. Is there a correct method of passing multiple or parameters, the https://developer.github.com/v3/#parameters page doesn't explicitly mention it and I am having no luck trying suggested methods, e.g. ?status=in_progress&status=queued
... View more
I'm wondering why the https://developer.github.com/v3/repos/#create-a-repository-dispatch-event response is `204: no-content`, could it not return a pointer to the job that is created? It doesn't seem as HATEOS as the rest of teh endpoints I'm trying to build a bot that triggers a long running test suite via action, currently I have to poll <repo> /actions/workflows/manual-integration-tests.yml/runs?status=in_progress until a job exists, get the run_url and then poll that until the status changes. Is there a better method of finding the job I triggered? Or am I fundamentally missing the point of repository_dispatch events?
... View more