You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Sources/rate-limit/Client.swift
+4-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,8 @@ public struct Client: APIProtocol {
40
40
}
41
41
/// Get rate limit status for the authenticated user
42
42
///
43
-
/// **Note:** Accessing this endpoint does not count against your REST API rate limit.
43
+
/// > [!NOTE]
44
+
/// > Accessing this endpoint does not count against your REST API rate limit.
44
45
///
45
46
/// Some categories of endpoints have custom rate limits that are separate from the rate limit governing the other REST API endpoints. For this reason, the API response categorizes your rate limit. Under `resources`, you'll see objects relating to different categories:
46
47
/// * The `core` object provides your rate limit status for all non-search-related resources in the REST API.
@@ -53,7 +54,8 @@ public struct Client: APIProtocol {
53
54
/// * The `actions_runner_registration` object provides your rate limit status for registering self-hosted runners in GitHub Actions. For more information, see "[Self-hosted runners](https://docs.github.com/rest/actions/self-hosted-runners)."
54
55
/// * The `source_import` object is no longer in use for any API endpoints, and it will be removed in the next API version. For more information about API versions, see "[API Versions](https://docs.github.com/rest/about-the-rest-api/api-versions)."
55
56
///
56
-
/// **Note:** The `rate` object is deprecated. If you're writing new API client code or updating existing code, you should use the `core` object instead of the `rate` object. The `core` object contains the same information that is present in the `rate` object.
57
+
/// > [!NOTE]
58
+
/// > The `rate` object is deprecated. If you're writing new API client code or updating existing code, you should use the `core` object instead of the `rate` object. The `core` object contains the same information that is present in the `rate` object.
57
59
///
58
60
/// - Remark: HTTP `GET /rate_limit`.
59
61
/// - Remark: Generated from `#/paths//rate_limit/get(rate-limit/get)`.
Copy file name to clipboardExpand all lines: Sources/rate-limit/Types.swift
+12-6Lines changed: 12 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,8 @@ import struct Foundation.Date
13
13
publicprotocolAPIProtocol:Sendable{
14
14
/// Get rate limit status for the authenticated user
15
15
///
16
-
/// **Note:** Accessing this endpoint does not count against your REST API rate limit.
16
+
/// > [!NOTE]
17
+
/// > Accessing this endpoint does not count against your REST API rate limit.
17
18
///
18
19
/// Some categories of endpoints have custom rate limits that are separate from the rate limit governing the other REST API endpoints. For this reason, the API response categorizes your rate limit. Under `resources`, you'll see objects relating to different categories:
19
20
/// * The `core` object provides your rate limit status for all non-search-related resources in the REST API.
@@ -26,7 +27,8 @@ public protocol APIProtocol: Sendable {
26
27
/// * The `actions_runner_registration` object provides your rate limit status for registering self-hosted runners in GitHub Actions. For more information, see "[Self-hosted runners](https://docs.github.com/rest/actions/self-hosted-runners)."
27
28
/// * The `source_import` object is no longer in use for any API endpoints, and it will be removed in the next API version. For more information about API versions, see "[API Versions](https://docs.github.com/rest/about-the-rest-api/api-versions)."
28
29
///
29
-
/// **Note:** The `rate` object is deprecated. If you're writing new API client code or updating existing code, you should use the `core` object instead of the `rate` object. The `core` object contains the same information that is present in the `rate` object.
30
+
/// > [!NOTE]
31
+
/// > The `rate` object is deprecated. If you're writing new API client code or updating existing code, you should use the `core` object instead of the `rate` object. The `core` object contains the same information that is present in the `rate` object.
30
32
///
31
33
/// - Remark: HTTP `GET /rate_limit`.
32
34
/// - Remark: Generated from `#/paths//rate_limit/get(rate-limit/get)`.
@@ -37,7 +39,8 @@ public protocol APIProtocol: Sendable {
37
39
extensionAPIProtocol{
38
40
/// Get rate limit status for the authenticated user
39
41
///
40
-
/// **Note:** Accessing this endpoint does not count against your REST API rate limit.
42
+
/// > [!NOTE]
43
+
/// > Accessing this endpoint does not count against your REST API rate limit.
41
44
///
42
45
/// Some categories of endpoints have custom rate limits that are separate from the rate limit governing the other REST API endpoints. For this reason, the API response categorizes your rate limit. Under `resources`, you'll see objects relating to different categories:
43
46
/// * The `core` object provides your rate limit status for all non-search-related resources in the REST API.
@@ -50,7 +53,8 @@ extension APIProtocol {
50
53
/// * The `actions_runner_registration` object provides your rate limit status for registering self-hosted runners in GitHub Actions. For more information, see "[Self-hosted runners](https://docs.github.com/rest/actions/self-hosted-runners)."
51
54
/// * The `source_import` object is no longer in use for any API endpoints, and it will be removed in the next API version. For more information about API versions, see "[API Versions](https://docs.github.com/rest/about-the-rest-api/api-versions)."
52
55
///
53
-
/// **Note:** The `rate` object is deprecated. If you're writing new API client code or updating existing code, you should use the `core` object instead of the `rate` object. The `core` object contains the same information that is present in the `rate` object.
56
+
/// > [!NOTE]
57
+
/// > The `rate` object is deprecated. If you're writing new API client code or updating existing code, you should use the `core` object instead of the `rate` object. The `core` object contains the same information that is present in the `rate` object.
54
58
///
55
59
/// - Remark: HTTP `GET /rate_limit`.
56
60
/// - Remark: Generated from `#/paths//rate_limit/get(rate-limit/get)`.
@@ -296,7 +300,8 @@ public enum Components {
296
300
publicenumOperations{
297
301
/// Get rate limit status for the authenticated user
298
302
///
299
-
/// **Note:** Accessing this endpoint does not count against your REST API rate limit.
303
+
/// > [!NOTE]
304
+
/// > Accessing this endpoint does not count against your REST API rate limit.
300
305
///
301
306
/// Some categories of endpoints have custom rate limits that are separate from the rate limit governing the other REST API endpoints. For this reason, the API response categorizes your rate limit. Under `resources`, you'll see objects relating to different categories:
302
307
/// * The `core` object provides your rate limit status for all non-search-related resources in the REST API.
@@ -309,7 +314,8 @@ public enum Operations {
309
314
/// * The `actions_runner_registration` object provides your rate limit status for registering self-hosted runners in GitHub Actions. For more information, see "[Self-hosted runners](https://docs.github.com/rest/actions/self-hosted-runners)."
310
315
/// * The `source_import` object is no longer in use for any API endpoints, and it will be removed in the next API version. For more information about API versions, see "[API Versions](https://docs.github.com/rest/about-the-rest-api/api-versions)."
311
316
///
312
-
/// **Note:** The `rate` object is deprecated. If you're writing new API client code or updating existing code, you should use the `core` object instead of the `rate` object. The `core` object contains the same information that is present in the `rate` object.
317
+
/// > [!NOTE]
318
+
/// > The `rate` object is deprecated. If you're writing new API client code or updating existing code, you should use the `core` object instead of the `rate` object. The `core` object contains the same information that is present in the `rate` object.
313
319
///
314
320
/// - Remark: HTTP `GET /rate_limit`.
315
321
/// - Remark: Generated from `#/paths//rate_limit/get(rate-limit/get)`.
0 commit comments