* Fix handling nil values for optional string array parameters,
nil values should be equivalent to an empty string, currently we return an error but Claude passes nil for optional values.
* lint fixes
Page size tool parameter names were changed to `perPage` within #90
while GitHub API uses `per_page` parameter name.
This change fixes overlooked inconsistencies.
Follow up on #90
Follow up on #129Fixes#136
Signed-off-by: Alexander Yastrebov <yastrebov.alex@gmail.com>
* Add line parameter support to create_pull_request_review tool
- Updated schema to make path and body the only required fields
- Added line parameter as alternative to position for inline comments
- Updated handler to accept either position or line based on GitHub API spec
- Added new test case that verifies line parameter works properly
- Updated error messages for better validation
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Expand PR review API with multi-line comment support
- Added new parameters: line, side, start_line, start_side
- Added proper validation for multi-line comment parameters
- Improved validation logic to handle parameter combinations
- Added test cases for regular and multi-line comments
- Updated schema documentation for better tool discoverability
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* gofmt
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Javier Uruen Val <juruen@github.com>
* Add support for retrieving GitHub Issue Comments
Add new tool 'get_issue_comments' that allows fetching comments associated
with GitHub issues. This complements the existing issue retrieval functionality
and follows the same patterns as the pull request comments implementation.
The implementation includes:
- New getIssueComments function in pkg/github/issues.go
- Tool registration in server.go
- Comprehensive test coverage in issues_test.go
* Support pagination for get_issue_comments
---------
Co-authored-by: Javier Uruen Val <juruen@github.com>
* refactor to make testing easier
* not needed in handler func
* small cleanup
* create repository_resource_test
* remove chatty comments
* comment cleanup, function rename and some more tests
* fix test for ubuntu runner
* remove it for now
* make required args explicit instead of panic
* more tests and cleanup
* chore: use raw repo resources (#70)
* use raw repo URIs for resources
* fetch repository content from raw urls
* ensure no error in test write
* Update pkg/github/repository_resource.go
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* use appropriate file name for text file test
---------
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
---------
Co-authored-by: Sam Morrow <info@sam-morrow.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This was causing issues in the Docker container, where viper looks for a
filename, without considering the extension, resulting in it trying to
parse the binary itself as JSON.
William Martin