The vscode configuration example in the README.md does not work with my version of vscode. Since it's also not required, this change removes it so that it works in all versions of vscode.
Version:
```
Version: 1.99.1 (Universal)
Commit: 7c6fdfb0b8f2f675eb0b47f3d95eeca78962565b
Date: 2025-04-04T15:58:59.624Z (4 days ago)
Electron: 34.3.2
ElectronBuildId: 11161073
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin x64 24.3.0
```
License Check / license-check (push) Has been cancelled
CodeQL / Analyze (go) (push) Has been cancelled
CodeQL / Analyze (actions) (push) Has been cancelled
Docker / build (push) Has been cancelled
Unit Tests / build (macos-latest) (push) Has been cancelled
Unit Tests / build (ubuntu-latest) (push) Has been cancelled
Unit Tests / build (windows-latest) (push) Has been cancelled
GoReleaser Release / release (push) Has been cancelled
Lint / lint (push) Has been cancelled
Windsurf is erroring on the `create_pull_request` tool because we're
using an array of types to make fields nullable. This PR uses `anyOf`
instead and should fix the issue.
* Update README.md to explain Agent mode will start the server
* Update README.md
Co-authored-by: Sam Morrow <info@sam-morrow.com>
---------
Co-authored-by: Sam Morrow <info@sam-morrow.com>
* Add add_pull_request_review_comment tool for PR review comments
Adds the ability to add review comments to pull requests with support for line, multi-line, and file-level comments, as well as replying to existing comments.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Add reply_to_pull_request_review_comment tool
Adds a new tool to reply to existing pull request review comments using the GitHub API's comment reply endpoint. This allows for threaded discussions on pull request reviews.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Update README with new PR review comment tools
* rebase
* use new getClient function inadd and reply pr review tools
* Unify PR review comment tools into a single consolidated tool
The separate AddPullRequestReviewComment and ReplyToPullRequestReviewComment tools have been merged into a single tool that handles both creating new comments and replying to existing ones. This approach simplifies the API and provides a more consistent interface for users.
- Made commit_id and path optional when using in_reply_to for replies
- Updated the tests to verify both comment and reply functionality
- Removed the separate ReplyToPullRequestReviewComment tool
- Fixed test expectations to match how errors are returned
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Update README to reflect the unified PR review comment tool
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Javier Uruen Val <juruen@github.com>
* Add ability to view branches for a repo #141
* fix: update ListBranches test to use InputSchema and correct translation helper
* fix: update ListBranches test to use InputSchema and correct translation helper
* fix: update ListBranches test to handle errors in tool result
* fix: replace deprecated github.String with github.Ptr
* docs: add list_branches tool documentation to README
Currently PRs are not being automatically requested for review because the CODEOWNERS file is missing a `*`.
Co-authored-by: Javier Uruen Val <juruen@github.com>
* 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
Xavier RENE-CORAIL