[BUG]: There's no WorkflowJobStatus.Waiting

[vuryleo]

What happened?

While querying for the workflow job status, suddenly it returns sth other than queued in_progress nor completed but waiting.
As it's waiting for some prod approval.

Versions

octoket v6.1.0

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[kfcampbell]

Interesting...it seems like that was missed in the specification. The docs here show the following options:

    "status": {
      "description": "The phase of the lifecycle that the job is currently in.",
      "type": "string",
      "enum": [
        "queued",
        "in_progress",
        "completed"
      ],
      "examples": [
        "queued"
      ]
    },

but I do see where the API returns waiting.

[kfcampbell]

I've asked around internally about why this may be the case, and I'll follow up here before taking action on your PR. Thanks!

[kfcampbell]

It seems like there's several API schemas that do and do not have "waiting" as a status. The docs linked above also have a "Get a job for a workflow run" endpoint that returns (in part):

    "status": {
      "description": "The phase of the lifecycle that the job is currently in.",
      "type": "string",
      "enum": [
        "queued",
        "in_progress",
        "completed"
      ],
      "examples": [
        "queued"
      ]
    },

Since Octokit.net has one model we share across these endpoints, your PR looks reasonable.

[vuryleo]

Yes, however, in my case it's just returning as a response from a get a workflowjob API. Perhaps the document is kind of outdated.