feat: add get_file_blame tool for retrieving git blame information #1538
+575
−1
Conversation
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
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a new get_file_blame tool that enables users to retrieve git blame information for files in GitHub repositories using the GraphQL API. The implementation includes comprehensive test coverage, proper error handling, and complete documentation updates.
Key Changes
- Added
GetFileBlamefunction that queries GitHub's GraphQL API to retrieve blame information showing who last modified each line of a file - Integrated the new tool into the default toolset alongside other repository management tools
- Created comprehensive unit tests covering successful operations, error scenarios, and edge cases like missing default branches
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| pkg/github/repositories.go | Implements the GetFileBlame tool with GraphQL queries for default branch resolution and blame data retrieval, including proper type conversions and JSON response formatting |
| pkg/github/tools.go | Registers GetFileBlame in the DefaultToolsetGroup for availability in the standard tool collection |
| pkg/github/repositories_test.go | Adds comprehensive test coverage including tool schema validation, default branch handling, specific ref queries, and error scenarios |
| pkg/github/toolsnaps/get_file_blame.snap | Tool schema snapshot documenting the API surface with ReadOnly annotation |
| README.md | Documents the new tool with parameter descriptions and usage information |
MayorFaj
force-pushed
the
feat/git-blame-tool
branch
from
1222293 to
8e494d9
Compare
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 a new tool for retrieving git blame information for files in a GitHub repository, along with comprehensive tests and documentation updates. The main focus is on enabling users to see who last modified each line in a file, with support for specifying branches, tags, or commit SHAs.
New Git Blame Tool Integration
get_file_blametool to the codebase, which uses the GitHub GraphQL API to fetch blame information for a file, including author details, commit SHA, message, and line ranges. The tool supports specifying the repository owner, name, file path, and git reference, defaulting to the repository's default branch if not provided. (pkg/github/repositories.go)get_file_blametool in the default toolset group so it is available for use alongside other repository tools. (pkg/github/tools.go)Documentation and Tool Snapshots
README.mdto document the newget_file_blametool, including its parameters and usage.get_file_blamefor validation and testing purposes. (pkg/github/__toolsnaps__/get_file_blame.snap)Closes: #504