docs(skills): clarify /search/issues returns issues and PRs - #2713
Conversation
Add a bullet noting the unified /search/issues endpoint returns both issues and pull requests and there is no /search/pulls endpoint. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
size: XS
There was a problem hiding this comment.
Pull request overview
Updates the GitHub skill documentation to clarify that the REST Search API uses a single /search/issues endpoint for both issues and pull requests, and that filtering is done via is:pr / is:issue.
Changes:
- Add a bullet under the Search section clarifying
/search/issuesreturns both issues and PRs and there is no/search/pulls.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the GitHub skill documentation to clarify that the /search/issues endpoint handles both issues and pull requests. A review comment suggests simplifying this new note to avoid redundancy with existing headers while maintaining the key information about the lack of a dedicated /search/pulls endpoint.
| http(method="GET", url="https://api.github.com/search/issues?q=repo:{owner}/{repo}+is:pr+is:open+label:bug") | ||
| ``` | ||
|
|
||
| - The unified endpoint `/search/issues` returns BOTH issues and pull requests — there is no `/search/pulls` endpoint. Use `is:pr` or `is:issue` in the `q=` filter to narrow the results. |
There was a problem hiding this comment.
The added clarification is helpful, but it repeats information already present in the section header (line 139), specifically the instruction to use is:pr or is:issue. To improve conciseness and avoid redundancy, consider simplifying the note to focus on the absence of the /search/pulls endpoint.
| - The unified endpoint `/search/issues` returns BOTH issues and pull requests — there is no `/search/pulls` endpoint. Use `is:pr` or `is:issue` in the `q=` filter to narrow the results. | |
| - Note: There is no /search/pulls endpoint; /search/issues is the unified endpoint for both issues and PRs. |
There was a problem hiding this comment.
Simplified the bullet as suggested — dropped the redundant is:pr/is:issue guidance (already in the section header) and kept the note focused on the absence of /search/pulls. Fixed in d9fcba3.
Addresses gemini-code-assist review on PR #2713: trim redundancy with the section header and focus the note on the absence of a /search/pulls endpoint. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
) * docs(skills): clarify /search/issues returns issues and PRs Add a bullet noting the unified /search/issues endpoint returns both issues and pull requests and there is no /search/pulls endpoint. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(skills): simplify /search/issues bullet per review Addresses gemini-code-assist review on PR nearai#2713: trim redundancy with the section header and focus the note on the absence of a /search/pulls endpoint. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Summary
skills/github/SKILL.mdnoting that the unified/search/issuesendpoint returns BOTH issues and pull requests, and that there is no/search/pullsendpoint.is:pr/is:issuefilters used throughout the existing examples.Test plan
🤖 Generated with Claude Code