Add update project item tool

[JoannaaKL]

This pr:

• adds tool to update project item for an user or org
• formats all project tools to follow formatting standard
  Closes: Add support for Projects #44 (comment)

[Copilot]

Pull Request Overview

This PR adds a new tool to update project items for users or organizations, addressing issue #44. The implementation follows the existing pattern of project item management tools by adding the UpdateProjectItem function with comprehensive validation and testing.

• Add UpdateProjectItem tool function with field update capabilities
• Implement comprehensive test coverage with error handling scenarios
• Update project item data structures to support additional fields

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
pkg/github/tools.go	Registers the new UpdateProjectItem tool in the write toolset
pkg/github/projects.go	Implements UpdateProjectItem function with validation and API call logic
pkg/github/projects_test.go	Adds comprehensive test suite covering success and error scenarios
pkg/github/minimal_types.go	Extends MinimalProjectItem struct with Title and Description fields
pkg/github/toolsnaps/update_project_item.snap	Tool schema snapshot for testing validation
README.md	Documents the new update_project_item tool parameters

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[tonytrg]

I am having a hard time understanding new_field, not too familiar with the api of projects but it seems hard to understand to me only from the mcps side of description.

https://docs.github.com/en/rest/projects/items?apiVersion=2022-11-28#update-project-item-for-organization--parameters

fields array of objects Required
A list of field updates to apply.

id integer Required
The ID of the project field to update.

value null or string or number Required
The new value for the field:

For text, number, and date fields, provide the new value directly.
For single select and iteration fields, provide the ID of the option or iteration.
To clear the field, set this to null.

[tonytrg]

seems like we are looking for a map struct.

Should it look something like this

 mcp.Items(
map[string]interface{}{
"type": "string",
},
),

[tonytrg]

I am not sure if we can rely on the llm to always understand and format a correct parseable struct

[tonytrg]

ah ok i see it needs to be more flexible

 mcp.WithObject("new_field",
mcp.Required(),
mcp.Description("Object consisting of the ID of the project field to update and the new value for the field. To clear the field, set \"value\" to null."),
mcp.Properties(map[string]any{
"id": map[string]any{
"type": "number",
"description": "The ID of the project field to update (required)",
},
"value": map[string]any{
"description": "The new value for the field. Can be a string for text fields, a number for number/single_select/iteration fields, or null to clear the field (required)",
},
}),

would something like that help?

[almaleksia]

I'd propose we split it into 2 fields which is field_id and field_value

[JoannaaKL]

How the types would look like then? We can use WithNumber for the field_id but field value needs to stay an object

[JoannaaKL]

We can do it 👍

[tonytrg]

@almaleksia@JoannaaKL i updated the struct the one before was wrong

[tonytrg]

💯 thanks for making this complicated one work

note for future as i dont want to block this merge:

• correct parsing of the iteration ids is missing right now, but as that actually should be part of the sdk we can fix that later on