diff --git a/cache/api.github.com.deref.json b/cache/api.github.com.deref.json index cee75799..f40930c6 100644 --- a/cache/api.github.com.deref.json +++ b/cache/api.github.com.deref.json @@ -21168,7 +21168,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -140950,7 +140950,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -146181,7 +146183,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -153639,7 +153641,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -154498,7 +154502,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -158102,7 +158108,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -182173,11 +182179,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -182488,13 +182497,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -183546,13 +183558,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -184490,11 +184505,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -184769,13 +184787,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -186053,11 +186074,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -187525,11 +187550,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -190052,11 +190081,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -191656,13 +191689,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -214441,13 +214477,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -215457,11 +215496,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -467540,7 +467583,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/cache/api.github.com.json b/cache/api.github.com.json index 889e0088..b5715da5 100644 --- a/cache/api.github.com.json +++ b/cache/api.github.com.json @@ -2297,7 +2297,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -28747,11 +28747,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -29141,11 +29144,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -61875,7 +61881,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -100817,7 +100823,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -103505,13 +103513,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -103789,11 +103800,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -307398,7 +307413,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { diff --git a/cache/ghec.deref.json b/cache/ghec.deref.json index 4480fb8f..6dd308e5 100644 --- a/cache/ghec.deref.json +++ b/cache/ghec.deref.json @@ -30205,7 +30205,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Cloud provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Cloud global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-cloud@latest//rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Cloud.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-cloud@latest//rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Cloud global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-cloud@latest//rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Cloud.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-cloud@latest//rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-cloud@latest//rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -157654,7 +157654,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -162887,7 +162889,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -170417,7 +170419,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -171276,7 +171280,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -174880,7 +174886,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -198975,11 +198981,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -199290,13 +199299,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -200348,13 +200360,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -201292,11 +201307,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -201571,13 +201589,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -202855,11 +202876,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -204339,11 +204364,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -206890,11 +206919,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -208506,13 +208539,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -231339,13 +231375,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -232355,11 +232394,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -495385,7 +495428,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/cache/ghec.json b/cache/ghec.json index 77adba48..10f9a92a 100644 --- a/cache/ghec.json +++ b/cache/ghec.json @@ -5038,7 +5038,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Cloud provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Cloud global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-cloud@latest//rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Cloud.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-cloud@latest//rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Cloud global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-cloud@latest//rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Cloud.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-cloud@latest//rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-cloud@latest//rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -33745,11 +33745,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -34139,11 +34142,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -68803,7 +68809,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -109145,7 +109151,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -111834,13 +111842,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -112118,11 +112129,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -317808,7 +317823,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { diff --git a/cache/ghes-3.10.deref.json b/cache/ghes-3.10.deref.json index 3080feb5..78deb0b7 100644 --- a/cache/ghes-3.10.deref.json +++ b/cache/ghes-3.10.deref.json @@ -41799,7 +41799,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.10/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.10/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.10/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.10/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.10/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -139787,7 +139787,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -145022,7 +145024,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -152358,7 +152360,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -153121,7 +153125,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -156495,7 +156501,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -179963,11 +179969,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -180278,13 +180287,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -181336,13 +181348,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -182280,11 +182295,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -182559,13 +182577,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -183843,11 +183864,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -185315,11 +185340,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -187842,11 +187871,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -189446,13 +189479,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -204259,13 +204295,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -205275,11 +205314,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -415218,7 +415261,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/cache/ghes-3.10.json b/cache/ghes-3.10.json index 0bf5b26c..9ac612ba 100644 --- a/cache/ghes-3.10.json +++ b/cache/ghes-3.10.json @@ -7643,7 +7643,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.10/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.10/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.10/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.10/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.10/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -31158,11 +31158,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -31552,11 +31555,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -60443,7 +60449,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -99376,7 +99382,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -101847,13 +101855,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -102131,11 +102142,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -293857,7 +293872,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { diff --git a/cache/ghes-3.11.deref.json b/cache/ghes-3.11.deref.json index 82872e86..c60c1973 100644 --- a/cache/ghes-3.11.deref.json +++ b/cache/ghes-3.11.deref.json @@ -43181,7 +43181,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.11/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.11/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.11/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.11/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.11/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -146854,7 +146854,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -152097,7 +152099,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -159433,7 +159435,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -160196,7 +160200,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -163570,7 +163576,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -187434,11 +187440,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -187749,13 +187758,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -188807,13 +188819,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -189751,11 +189766,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -190030,13 +190048,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -191314,11 +191335,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -192786,11 +192811,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -195313,11 +195342,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -196917,13 +196950,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -211740,13 +211776,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -212756,11 +212795,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -429203,7 +429246,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/cache/ghes-3.11.json b/cache/ghes-3.11.json index 900b8534..54faffca 100644 --- a/cache/ghes-3.11.json +++ b/cache/ghes-3.11.json @@ -7921,7 +7921,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.11/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.11/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.11/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.11/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.11/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -32044,11 +32044,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -32438,11 +32441,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -61849,7 +61855,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -102482,7 +102488,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -105015,13 +105023,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -105299,11 +105310,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -297961,7 +297976,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { diff --git a/cache/ghes-3.12.deref.json b/cache/ghes-3.12.deref.json index a26a8bc0..f414194b 100644 --- a/cache/ghes-3.12.deref.json +++ b/cache/ghes-3.12.deref.json @@ -43544,7 +43544,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.12/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.12/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.12/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.12/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.12/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -149360,7 +149360,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -154603,7 +154605,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -161939,7 +161941,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -162798,7 +162802,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -166172,7 +166178,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -190036,11 +190042,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -190351,13 +190360,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -191409,13 +191421,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -192353,11 +192368,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -192632,13 +192650,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -193916,11 +193937,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -195388,11 +195413,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -197915,11 +197944,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -199519,13 +199552,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -214339,13 +214375,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -215355,11 +215394,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -432496,7 +432539,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/cache/ghes-3.12.json b/cache/ghes-3.12.json index 0859ac18..2b52378e 100644 --- a/cache/ghes-3.12.json +++ b/cache/ghes-3.12.json @@ -7924,7 +7924,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.12/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.12/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.12/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.12/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.12/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -32870,11 +32870,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -33264,11 +33267,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -62812,7 +62818,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -104578,7 +104584,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -107111,13 +107119,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -107395,11 +107406,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -300565,7 +300580,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { diff --git a/cache/ghes-3.8.deref.json b/cache/ghes-3.8.deref.json index 09bbe9e4..32738c48 100644 --- a/cache/ghes-3.8.deref.json +++ b/cache/ghes-3.8.deref.json @@ -41232,7 +41232,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.8/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.8/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.8/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.8/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.8/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -127851,7 +127851,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -132520,7 +132522,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -139520,7 +139522,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -140159,7 +140163,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -143517,7 +143523,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -166640,11 +166646,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -166955,13 +166964,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -168013,13 +168025,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -168957,11 +168972,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -169236,13 +169254,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -170520,11 +170541,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -171936,11 +171961,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -174351,11 +174380,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -175899,13 +175932,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -190277,13 +190313,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -191293,11 +191332,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -393424,7 +393467,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/cache/ghes-3.8.json b/cache/ghes-3.8.json index 18cc768a..352a1583 100644 --- a/cache/ghes-3.8.json +++ b/cache/ghes-3.8.json @@ -7499,7 +7499,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.8/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.8/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.8/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.8/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.8/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -28696,11 +28696,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -29090,11 +29093,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -56604,7 +56610,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -92533,7 +92539,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -94931,13 +94939,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -95215,11 +95226,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -284608,7 +284623,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { diff --git a/cache/ghes-3.9.deref.json b/cache/ghes-3.9.deref.json index 9ae504b6..5d1cfbd9 100644 --- a/cache/ghes-3.9.deref.json +++ b/cache/ghes-3.9.deref.json @@ -41428,7 +41428,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.9/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.9/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.9/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.9/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.9/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -134698,7 +134698,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -139653,7 +139655,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -146905,7 +146907,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -147551,7 +147555,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -150916,7 +150922,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -174104,11 +174110,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -174419,13 +174428,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -175477,13 +175489,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -176421,11 +176436,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -176700,13 +176718,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -177984,11 +178005,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -179442,11 +179467,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -181941,11 +181970,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -183531,13 +183564,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -198319,13 +198355,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -199335,11 +199374,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -408058,7 +408101,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/cache/ghes-3.9.json b/cache/ghes-3.9.json index bb38ba79..ef348671 100644 --- a/cache/ghes-3.9.json +++ b/cache/ghes-3.9.json @@ -7520,7 +7520,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.9/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.9/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.9/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.9/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.9/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -29904,11 +29904,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "default": "queued" }, @@ -30298,11 +30301,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -58863,7 +58869,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -96955,7 +96961,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -99360,13 +99368,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -99644,11 +99655,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -290452,7 +290467,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { diff --git a/generated/api.github.com.deref.json b/generated/api.github.com.deref.json index 95e23889..2ea5882b 100644 --- a/generated/api.github.com.deref.json +++ b/generated/api.github.com.deref.json @@ -21093,7 +21093,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -141209,7 +141209,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -146477,7 +146479,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -153942,7 +153944,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -154806,7 +154810,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -158433,7 +158439,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -183830,13 +183836,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -184775,11 +184784,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -185054,13 +185066,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -186341,11 +186356,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -187813,11 +187832,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -190342,11 +190365,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -191947,13 +191974,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -214769,13 +214799,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -215786,11 +215819,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -469835,7 +469872,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/generated/api.github.com.json b/generated/api.github.com.json index 2f94ad35..feaf6731 100644 --- a/generated/api.github.com.json +++ b/generated/api.github.com.json @@ -3039,7 +3039,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -30243,11 +30243,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -63630,7 +63633,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -102672,7 +102675,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -105360,13 +105365,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -105644,11 +105652,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -309253,7 +309265,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { diff --git a/generated/ghec.deref.json b/generated/ghec.deref.json index 6e12f3a8..6c0d44a0 100644 --- a/generated/ghec.deref.json +++ b/generated/ghec.deref.json @@ -30192,7 +30192,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Cloud provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Cloud global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-cloud@latest//rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Cloud.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-cloud@latest//rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Cloud global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-cloud@latest//rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Cloud.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-cloud@latest//rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-cloud@latest//rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -158015,7 +158015,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -163285,7 +163287,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -170822,7 +170824,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -171686,7 +171690,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -175313,7 +175319,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -200734,13 +200740,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -201679,11 +201688,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -201958,13 +201970,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -203245,11 +203260,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -204729,11 +204748,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -207282,11 +207305,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -208899,13 +208926,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -231798,13 +231828,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -232815,11 +232848,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -497833,7 +497870,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/generated/ghec.json b/generated/ghec.json index a8933e2e..f10a71ae 100644 --- a/generated/ghec.json +++ b/generated/ghec.json @@ -5842,7 +5842,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Cloud provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Cloud global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-cloud@latest//rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Cloud.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-cloud@latest//rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Cloud global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-cloud@latest//rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Cloud.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-cloud@latest//rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-cloud@latest//rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -35343,11 +35343,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -70690,7 +70693,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -111132,7 +111135,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -113821,13 +113826,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -114105,11 +114113,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -319795,7 +319807,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { diff --git a/generated/ghes-3.10.deref.json b/generated/ghes-3.10.deref.json index 5097dc24..4d7dc73e 100644 --- a/generated/ghes-3.10.deref.json +++ b/generated/ghes-3.10.deref.json @@ -41854,7 +41854,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.10/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.10/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.10/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.10/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.10/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -140131,7 +140131,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -145403,7 +145405,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -152745,7 +152747,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -153512,7 +153516,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -156908,7 +156914,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -181698,13 +181704,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -182643,11 +182652,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -182922,13 +182934,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -184209,11 +184224,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -185681,11 +185700,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -188210,11 +188233,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -189815,13 +189842,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -204681,13 +204711,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -205698,11 +205731,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -417513,7 +417550,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/generated/ghes-3.10.json b/generated/ghes-3.10.json index cc9b88ad..c3562202 100644 --- a/generated/ghes-3.10.json +++ b/generated/ghes-3.10.json @@ -8490,7 +8490,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.10/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.10/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.10/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.10/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.10/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -32707,11 +32707,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -62152,7 +62155,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -101185,7 +101188,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -103656,13 +103661,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -103940,11 +103948,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -295666,7 +295678,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { diff --git a/generated/ghes-3.11.deref.json b/generated/ghes-3.11.deref.json index 0d405594..deecdaae 100644 --- a/generated/ghes-3.11.deref.json +++ b/generated/ghes-3.11.deref.json @@ -43238,7 +43238,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.11/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.11/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.11/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.11/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.11/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -147205,7 +147205,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -152485,7 +152487,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -159827,7 +159829,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -160594,7 +160598,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -163990,7 +163996,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -189177,13 +189183,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -190122,11 +190131,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -190401,13 +190413,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -191688,11 +191703,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -193160,11 +193179,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -195689,11 +195712,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -197294,13 +197321,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -212170,13 +212200,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -213187,11 +213220,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -431512,7 +431549,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/generated/ghes-3.11.json b/generated/ghes-3.11.json index 5caaa7f8..2835b529 100644 --- a/generated/ghes-3.11.json +++ b/generated/ghes-3.11.json @@ -8770,7 +8770,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.11/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.11/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.11/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.11/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.11/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -33601,11 +33601,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -63572,7 +63575,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -104305,7 +104308,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -106838,13 +106843,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -107122,11 +107130,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -299784,7 +299796,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { diff --git a/generated/ghes-3.12.deref.json b/generated/ghes-3.12.deref.json index b9d06a04..4e6ec877 100644 --- a/generated/ghes-3.12.deref.json +++ b/generated/ghes-3.12.deref.json @@ -43584,7 +43584,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.12/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.12/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.12/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.12/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.12/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -149706,7 +149706,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -154986,7 +154988,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -162328,7 +162330,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -163192,7 +163196,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -166588,7 +166594,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -191775,13 +191781,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -192720,11 +192729,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -192999,13 +193011,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -194286,11 +194301,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -195758,11 +195777,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -198287,11 +198310,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -199892,13 +199919,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -214765,13 +214795,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -215782,11 +215815,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -434803,7 +434840,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/generated/ghes-3.12.json b/generated/ghes-3.12.json index 6e140359..e875bb8b 100644 --- a/generated/ghes-3.12.json +++ b/generated/ghes-3.12.json @@ -8773,7 +8773,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.12/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.12/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.12/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.12/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.12/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -34440,11 +34440,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -64550,7 +64553,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -106416,7 +106419,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -108949,13 +108954,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -109233,11 +109241,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -302403,7 +302415,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { diff --git a/generated/ghes-3.8.deref.json b/generated/ghes-3.8.deref.json index 8a175892..8857390c 100644 --- a/generated/ghes-3.8.deref.json +++ b/generated/ghes-3.8.deref.json @@ -41293,7 +41293,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.8/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.8/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.8/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.8/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.8/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -128161,7 +128161,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -132864,7 +132866,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -139870,7 +139872,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -140512,7 +140516,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -143892,7 +143898,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -168336,13 +168342,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -169281,11 +169290,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -169560,13 +169572,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -170847,11 +170862,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -172263,11 +172282,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -174680,11 +174703,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -176229,13 +176256,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -190629,13 +190659,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -191646,11 +191679,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -395627,7 +395664,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/generated/ghes-3.8.json b/generated/ghes-3.8.json index b93a21f4..5775d25d 100644 --- a/generated/ghes-3.8.json +++ b/generated/ghes-3.8.json @@ -8344,7 +8344,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.8/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.8/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.8/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.8/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.8/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -30198,11 +30198,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -58224,7 +58227,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -94244,7 +94247,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -96642,13 +96647,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -96926,11 +96934,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -286319,7 +286331,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { diff --git a/generated/ghes-3.9.deref.json b/generated/ghes-3.9.deref.json index 4de4c15e..34bf3a2e 100644 --- a/generated/ghes-3.9.deref.json +++ b/generated/ghes-3.9.deref.json @@ -41481,7 +41481,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.9/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.9/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.9/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.9/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.9/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -135029,7 +135029,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -140020,7 +140022,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -147278,7 +147280,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -147927,7 +147931,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -151314,7 +151320,7 @@ }, { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": { @@ -175823,13 +175829,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -176768,11 +176777,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -177047,13 +177059,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -178334,11 +178349,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -179792,11 +179811,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -182293,11 +182316,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -183884,13 +183911,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -198696,13 +198726,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -199713,11 +199746,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -410313,7 +410350,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], diff --git a/generated/ghes-3.9.json b/generated/ghes-3.9.json index a2e593dd..3fe2b3c7 100644 --- a/generated/ghes-3.9.json +++ b/generated/ghes-3.9.json @@ -8365,7 +8365,7 @@ "/feeds": { "get": { "summary": "Get feeds", - "description": "GitHub Enterprise Server provides several timeline resources in [Atom](http://en.wikipedia.org/wiki/Atom_(standard)) format. The Feeds API lists all the feeds available to the authenticated user:\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.9/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.9/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", + "description": "Lists the feeds available to the authenticated user. The response provides a URL for each feed. You can then get a specific feed by sending a request to one of the feed URLs.\n\n* **Timeline**: The GitHub Enterprise Server global public timeline\n* **User**: The public timeline for any user, using `uri_template`. For more information, see \"[Hypermedia](https://docs.github.com/enterprise-server@3.9/rest/using-the-rest-api/getting-started-with-the-rest-api#hypermedia).\"\n* **Current user public**: The public timeline for the authenticated user\n* **Current user**: The private timeline for the authenticated user\n* **Current user actor**: The private timeline for activity created by the authenticated user\n* **Current user organizations**: The private timeline for the organizations the authenticated user is a member of.\n* **Security advisories**: A collection of public announcements that provide information about security-related vulnerabilities in software on GitHub Enterprise Server.\n\nBy default, timeline resources are returned in JSON. You can specify the `application/atom+xml` type in the `Accept` header to return timeline resources in Atom format. For more information, see \"[Media types](https://docs.github.com/enterprise-server@3.9/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types).\"\n\n**Note**: Private feeds are only returned when [authenticating via Basic Auth](https://docs.github.com/enterprise-server@3.9/rest/overview/other-authentication-methods#basic-authentication) since current feed URIs use the older, non revocable auth tokens.", "tags": [ "activity" ], @@ -31437,11 +31437,14 @@ }, "status": { "type": "string", - "description": "The current status.", + "description": "The current status of the check run. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -60543,7 +60546,7 @@ "/users/{username}/hovercard": { "get": { "summary": "Get contextual information for a user", - "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\nThe `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository via cURL, it would look like this:\n\n```shell\n curl -u username:token\n https://api.github.com/users/octocat/hovercard?subject_type=repository&subject_id=1300192\n```\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", + "description": "Provides hovercard information. You can find out more about someone in relation to their pull requests, issues, repositories, and organizations.\n\n The `subject_type` and `subject_id` parameters provide context for the person's hovercard, which returns more information than without the parameters. For example, if you wanted to find out more about `octocat` who owns the `Spoon-Knife` repository, you would use a `subject_type` value of `repository` and a `subject_id` value of `1300192` (the ID of the `Spoon-Knife` repository).\n\nOAuth app tokens and personal access tokens (classic) need the `repo` scope to use this endpoint.", "tags": [ "users" ], @@ -98735,7 +98738,9 @@ "queued", "in_progress", "completed", - "waiting" + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -101140,13 +101145,16 @@ "nullable": true }, "status": { - "description": "The phase of the lifecycle that the check is currently in.", + "description": "The phase of the lifecycle that the check is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check runs.", "example": "queued", "type": "string", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ] }, "conclusion": { @@ -101424,11 +101432,15 @@ }, "status": { "type": "string", + "description": "The phase of the lifecycle that the check suite is currently in. Statuses of waiting, requested, and pending are reserved for GitHub Actions check suites.", "example": "completed", "enum": [ "queued", "in_progress", - "completed" + "completed", + "waiting", + "requested", + "pending" ], "nullable": true }, @@ -292232,7 +292244,7 @@ }, "workflow-run-status": { "name": "status", - "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub can set a status of `waiting` or `requested`.", + "description": "Returns workflow runs with the check run `status` or `conclusion` that you specify. For example, a conclusion can be `success` or a status can be `in_progress`. Only GitHub Actions can set a status of `waiting`, `pending`, or `requested`.", "in": "query", "required": false, "schema": {