Commit via running ake Sources/issues

Author: dependabot[bot]

Sources/issues/Client.swift

@@ -44,10 +44,8 @@ public struct Client: APIProtocol {
     /// repositories, and organization repositories. You can use the `filter` query parameter to fetch issues that are not
     /// necessarily assigned to you.
     ///
-    /// **Note**: GitHub's REST API considers every pull request an issue, but not every issue is a pull request. For this
-    /// reason, "Issues" endpoints may return both issues and pull requests in the response. You can identify pull requests by
-    /// the `pull_request` key. Be aware that the `id` of a pull request returned from "Issues" endpoints will be an _issue id_. To find out the pull
-    /// request id, use the "[List pull requests](https://docs.github.com/rest/pulls/pulls#list-pull-requests)" endpoint.
+    /// > [!NOTE]
+    /// > GitHub's REST API considers every pull request an issue, but not every issue is a pull request. For this reason, "Issues" endpoints may return both issues and pull requests in the response. You can identify pull requests by the `pull_request` key. Be aware that the `id` of a pull request returned from "Issues" endpoints will be an _issue id_. To find out the pull request id, use the "[List pull requests](https://docs.github.com/rest/pulls/pulls#list-pull-requests)" endpoint.
     ///
     /// This endpoint supports the following custom media types. For more information, see "[Media types](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types)."
     ///
@@ -256,10 +254,8 @@ public struct Client: APIProtocol {
     ///
     /// List issues in an organization assigned to the authenticated user.
     ///
-    /// **Note**: GitHub's REST API considers every pull request an issue, but not every issue is a pull request. For this
-    /// reason, "Issues" endpoints may return both issues and pull requests in the response. You can identify pull requests by
-    /// the `pull_request` key. Be aware that the `id` of a pull request returned from "Issues" endpoints will be an _issue id_. To find out the pull
-    /// request id, use the "[List pull requests](https://docs.github.com/rest/pulls/pulls#list-pull-requests)" endpoint.
+    /// > [!NOTE]
+    /// > GitHub's REST API considers every pull request an issue, but not every issue is a pull request. For this reason, "Issues" endpoints may return both issues and pull requests in the response. You can identify pull requests by the `pull_request` key. Be aware that the `id` of a pull request returned from "Issues" endpoints will be an _issue id_. To find out the pull request id, use the "[List pull requests](https://docs.github.com/rest/pulls/pulls#list-pull-requests)" endpoint.
     ///
     /// This endpoint supports the following custom media types. For more information, see "[Media types](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types)."
     ///
@@ -599,10 +595,8 @@ public struct Client: APIProtocol {
     ///
     /// List issues in a repository. Only open issues will be listed.
     ///
-    /// **Note**: GitHub's REST API considers every pull request an issue, but not every issue is a pull request. For this
-    /// reason, "Issues" endpoints may return both issues and pull requests in the response. You can identify pull requests by
-    /// the `pull_request` key. Be aware that the `id` of a pull request returned from "Issues" endpoints will be an _issue id_. To find out the pull
-    /// request id, use the "[List pull requests](https://docs.github.com/rest/pulls/pulls#list-pull-requests)" endpoint.
+    /// > [!NOTE]
+    /// > GitHub's REST API considers every pull request an issue, but not every issue is a pull request. For this reason, "Issues" endpoints may return both issues and pull requests in the response. You can identify pull requests by the `pull_request` key. Be aware that the `id` of a pull request returned from "Issues" endpoints will be an _issue id_. To find out the pull request id, use the "[List pull requests](https://docs.github.com/rest/pulls/pulls#list-pull-requests)" endpoint.
     ///
     /// This endpoint supports the following custom media types. For more information, see "[Media types](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types)."
     ///
@@ -1708,10 +1702,8 @@ public struct Client: APIProtocol {
     /// access, the API returns a `410 Gone` status. To receive webhook events for transferred and deleted issues, subscribe
     /// to the [`issues`](https://docs.github.com/webhooks/event-payloads/#issues) webhook.
     ///
-    /// **Note**: GitHub's REST API considers every pull request an issue, but not every issue is a pull request. For this
-    /// reason, "Issues" endpoints may return both issues and pull requests in the response. You can identify pull requests by
-    /// the `pull_request` key. Be aware that the `id` of a pull request returned from "Issues" endpoints will be an _issue id_. To find out the pull
-    /// request id, use the "[List pull requests](https://docs.github.com/rest/pulls/pulls#list-pull-requests)" endpoint.
+    /// > [!NOTE]
+    /// > GitHub's REST API considers every pull request an issue, but not every issue is a pull request. For this reason, "Issues" endpoints may return both issues and pull requests in the response. You can identify pull requests by the `pull_request` key. Be aware that the `id` of a pull request returned from "Issues" endpoints will be an _issue id_. To find out the pull request id, use the "[List pull requests](https://docs.github.com/rest/pulls/pulls#list-pull-requests)" endpoint.
     ///
     /// This endpoint supports the following custom media types. For more information, see "[Media types](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types)."
     ///
@@ -4855,10 +4847,8 @@ public struct Client: APIProtocol {
     ///
     /// List issues across owned and member repositories assigned to the authenticated user.
     ///
-    /// **Note**: GitHub's REST API considers every pull request an issue, but not every issue is a pull request. For this
-    /// reason, "Issues" endpoints may return both issues and pull requests in the response. You can identify pull requests by
-    /// the `pull_request` key. Be aware that the `id` of a pull request returned from "Issues" endpoints will be an _issue id_. To find out the pull
-    /// request id, use the "[List pull requests](https://docs.github.com/rest/pulls/pulls#list-pull-requests)" endpoint.
+    /// > [!NOTE]
+    /// > GitHub's REST API considers every pull request an issue, but not every issue is a pull request. For this reason, "Issues" endpoints may return both issues and pull requests in the response. You can identify pull requests by the `pull_request` key. Be aware that the `id` of a pull request returned from "Issues" endpoints will be an _issue id_. To find out the pull request id, use the "[List pull requests](https://docs.github.com/rest/pulls/pulls#list-pull-requests)" endpoint.
     ///
     /// This endpoint supports the following custom media types. For more information, see "[Media types](https://docs.github.com/rest/using-the-rest-api/getting-started-with-the-rest-api#media-types)."
     ///