projects: add server instructions#1393
Merged
JoannaaKL merged 2 commits intotmelliottjr/update-projects-toolsfrom Nov 12, 2025
Merged
projects: add server instructions#1393JoannaaKL merged 2 commits intotmelliottjr/update-projects-toolsfrom
JoannaaKL merged 2 commits intotmelliottjr/update-projects-toolsfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds comprehensive server instructions for the GitHub Projects toolset to guide proper usage of project-related APIs. The new instructions cover workflow patterns, field handling, pagination requirements, query construction syntax, and common pitfalls to avoid.
Key Changes
- Added detailed "projects" case to the
getToolsetInstructionsfunction with multi-section guidance - Documented query construction heuristics and syntax essentials for filtering project items
- Provided pagination best practices and field validation requirements
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
grantschlarb1911-commits
approved these changes
Nov 11, 2025
kerobbi
approved these changes
Nov 11, 2025
JoannaaKL
approved these changes
Nov 11, 2025
|
|
||
| Return COMPLETE data or state what's missing (e.g. pages skipped). | ||
|
|
||
| list_project_items query rules: |
Contributor
There was a problem hiding this comment.
👋 this seems like it should live in the query param description in the list_project_items tool as it's specifically about that parameter in that tool?
JoannaaKL
merged commit 3c72fef
into
tmelliottjr/update-projects-tools
15 checks passed
kerobbi
pushed a commit
that referenced
this pull request
Nov 14, 2025
* pagination, serialization updates * projects: add server instructions (#1393) * add server instructions * Update instructions.go --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request adds comprehensive instructions for handling GitHub Projects to the
pkg/github/instructions.gofile. The new guidance covers best practices for listing, filtering, paginating, and summarizing project items, ensuring correct field usage and query construction. The changes are focused on improving clarity and accuracy when interacting with project-related APIs.Stacked on top of: #1390
These instructions help improve the quality of usage for projects related tools. Most specifically, those calls for listing project items. Some example query improvements below.
Example 1
Before:
updated:>2025-11-04After:
is:issue updated:>@today-7d priority:P0,P1,P2Example 2
Before:
assignee:rileyUltimately, no results were ever returned.
After:
Attempt 1:
is:issue assignee:rileyAttempt 2 (self-corrected):
is:issue assignee:*riley*Example 3
Before:
assignee:@me is:openAfter:
is:issue state:open priority:p1 assignee:@me