repo_search_commits: removing client-side-filters and updating the capabilities of the tool#1360
Open
krid-583 wants to merge 10 commits into
Open
Conversation
dpaquette
reviewed
Jun 15, 2026
krid-583
changed the title
krid-583
changed the title
dpaquette
requested changes
Jun 29, 2026
dpaquette
left a comment
dpaquette
left a comment
Contributor
There was a problem hiding this comment.
I like how much simpler this tool becomes. Just need to improve the argument descriptions a little
…s://github.com/krid-583/azure-devops-mcp into users/krid/repo-search-commits-description-fix
dpaquette
approved these changes
Jun 30, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Migrates the
repo_search_commitstool from the Git REST API(
GET _apis/git/repositories/{repo}/commits) to the Azure DevOpsSearch API (
POST almsearch.dev.azure.com/_apis/search/commitSearchResults).GitHub issue number
Closes #1327
Associated Risks
None
✅ PR Checklist
🧪 How did you test it?
Tested the updated unit tests.
Manually tested the tool.