I am facing an interesting problem with `repository_dispatch`, using it for a repo inside an GitHub org., when I use "my" access token, it's `204 No Content`, i.e a success,   but when I use token of any other member(same membership level as mine) in the repo, it's a 404 Not Found. The scopes are all the same for the generated token.   Any idea what could be happening? curl -i -X POST -H "Authorization: token <TOKEN>" -H "Accept: application/vnd.github.everest-preview+json" -H "Content-Type: application/json" --data '{"event_type":"add_user","client_payload":{"key":"value"}}' "https://api.github.com/repos/<ORG_NAME>/<REPO_NAME>/dispatches" Basically, just changing the `TOKEN` in the above snippet changes the behavior, even though the membership level and scopes are the same for another member in the org. ... View more

When I echo the context for `steps` as mentioned in the docs i get `{}` and `job` just has two fields.    GitHub Actions Contexts: https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions#contexts   Status check functions: https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions#status-check-functions   In the workflow syntax it is clear that `failure` should have been `failure()` https://help.github.com/en/articles/workflow-syntax-for-github-actions#example-using-status-check-functions   Currently selecting  on which ` step` 's success/failure should another step be triggered is not working it seems.   i.e steps: name: my first step if: job.steps.<step id>.status == failure ^ the above snippet from the doc is not working. ... View more