Repository navigation
chore(discovery): refresh Google Discovery index - #377
Merged
Merged
Conversation
Deploying grr-cli with
|
| Latest commit: |
c4847e6
|
| Status: | ⚡️ Build in progress... |
Contributor
Author
|
Code-affecting automation PR: auto-merge is enabled and this will squash-merge once all required checks pass. Never admin-merged — real CI gates a tree-changing merge. |
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
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.
Automated refresh of
src/discovery/from Google's DiscoveryService, run by
.github/workflows/discovery.yml. Theregenerated command tree (
src/commands/generated.rs), the agentskills (
skills/**), and the site's coverage table(
site/src/data/discovery-coverage.ts) ride along, so the PRalways contains the index and everything derived from it in
lockstep.
The Rust tests ran against this index, so a method whose shape
changed incompatibly would have failed the build rather than
shipping.
Review the diff for surprising removals — a method disappearing
usually means Google renamed it upstream.