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/search/Client.swift
+13-4Lines changed: 13 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -330,13 +330,22 @@ public struct Client: APIProtocol {
330
330
}
331
331
/// Search issues and pull requests
332
332
///
333
-
/// > [!WARNING]
334
-
/// > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
335
-
/// > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
333
+
/// Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api).
334
+
///
335
+
/// When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
336
+
/// search results, see [Text match metadata](https://docs.github.com/rest/search/search#text-match-metadata).
337
+
///
338
+
/// For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
/// This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
343
+
///
344
+
/// > [!NOTE]
345
+
/// > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
336
346
///
337
347
/// - Remark: HTTP `GET /search/issues`.
338
348
/// - Remark: Generated from `#/paths//search/issues/get(search/issues-and-pull-requests)`.
/// > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
58
-
/// > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
56
+
/// Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api).
57
+
///
58
+
/// When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
59
+
/// search results, see [Text match metadata](https://docs.github.com/rest/search/search#text-match-metadata).
60
+
///
61
+
/// For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
/// This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
66
+
///
67
+
/// > [!NOTE]
68
+
/// > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
59
69
///
60
70
/// - Remark: HTTP `GET /search/issues`.
61
71
/// - Remark: Generated from `#/paths//search/issues/get(search/issues-and-pull-requests)`.
/// > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
190
-
/// > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
197
+
/// Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api).
198
+
///
199
+
/// When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
200
+
/// search results, see [Text match metadata](https://docs.github.com/rest/search/search#text-match-metadata).
201
+
///
202
+
/// For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
/// This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
207
+
///
208
+
/// > [!NOTE]
209
+
/// > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
191
210
///
192
211
/// - Remark: HTTP `GET /search/issues`.
193
212
/// - Remark: Generated from `#/paths//search/issues/get(search/issues-and-pull-requests)`.
/// > **Notice:** Search for issues and pull requests will be overridden by advanced search on November 4, 2025.
5979
-
/// > You can read more about this change on [the GitHub blog](https://github.blog/changelog/2025-03-06-github-issues-projects-api-support-for-issues-advanced-search-and-more/).
5995
+
/// Find issues by state and keyword. This method returns up to 100 results [per page](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api).
5996
+
///
5997
+
/// When searching for issues, you can get text match metadata for the issue **title**, issue **body**, and issue **comment body** fields when you pass the `text-match` media type. For more details about how to receive highlighted
5998
+
/// search results, see [Text match metadata](https://docs.github.com/rest/search/search#text-match-metadata).
5999
+
///
6000
+
/// For example, if you want to find the oldest unresolved Python bugs on Windows. Your query might look something like this.
/// This query searches for the keyword `windows`, within any open issue that is labeled as `bug`. The search runs across repositories whose primary language is Python. The results are sorted by creation date in ascending order, which means the oldest issues appear first in the search results.
6005
+
///
6006
+
/// > [!NOTE]
6007
+
/// > For requests made by GitHub Apps with a user access token, you can't retrieve a combination of issues and pull requests in a single query. Requests that don't include the `is:issue` or `is:pull-request` qualifier will receive an HTTP `422 Unprocessable Entity` response. To get results for both issues and pull requests, you must send separate queries for issues and pull requests. For more information about the `is` qualifier, see "[Searching only issues or pull requests](https://docs.github.com/github/searching-for-information-on-github/searching-issues-and-pull-requests#search-only-issues-or-pull-requests)."
5980
6008
///
5981
6009
/// - Remark: HTTP `GET /search/issues`.
5982
6010
/// - Remark: Generated from `#/paths//search/issues/get(search/issues-and-pull-requests)`.
0 commit comments