-
Notifications
You must be signed in to change notification settings - Fork 207
Add pull request update tool #361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add pull request update tool #361
Conversation
- Add repo_update_pull_request tool for updating PR title, description, draft status, and target branch - Replace deprecated repo_update_pull_request_description with more flexible solution - Update documentation to reflect new tool capabilities - Add validation to ensure at least one field is provided for update - Support partial updates with optional parameters
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #361 +/- ##
=======================================
Coverage ? 75.20%
=======================================
Files ? 12
Lines ? 730
Branches ? 103
=======================================
Hits ? 549
Misses ? 176
Partials ? 5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
title: z.string().optional().describe("The new title for the pull request."), | ||
description: z.string().optional().describe("The new description for the pull request."), | ||
isDraft: z.boolean().optional().describe("Whether the pull request should be a draft."), | ||
targetRefName: z.string().optional().describe("The new target branch name (e.g., 'refs/heads/main')."), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you also add an optional parameter for status
in this tool, and then remove the update_pull_request_status
tool - they use the same node API, and it's better for the LLM to keep the number of tools down.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call. The description of the tool was a result of me trying to hint the model not to attempt to use this for status
. I've removed update_pull_request_status
and made the description align with the one used for update_work_item
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thank you @beauzeaux
GitHub issue number
322
Associated Risks
update_pull_request_status
andupdate_pull_request_reviewers
, neither of those operations can be accomplished with the underlying API✅ PR Checklist
🧪 How did you test it?