feat: expose CopilotToolNames for chip-service routing#48
Merged
bobby-smedley merged 1 commit intobot/mainfrom Apr 7, 2026
Merged
feat: expose CopilotToolNames for chip-service routing#48bobby-smedley merged 1 commit intobot/mainfrom
bobby-smedley merged 1 commit intobot/mainfrom
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
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
2 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.
Summary
Adds
CopilotToolNamesslice topkg/tools/register.golisting tool names that should be routed to the copilot service (discover_data_assets,discover_business_glossary).Why
chip-service needs to know which tools route to the copilot backend vs the standard DGC API. Previously it called
tools.NewAskDadTool()to get the name, but those constructors no longer exist after the sub-package restructure. This exposes the names cleanly without requiring chip-service to import individual sub-packages.Test plan
go build ./...passes