Terrence Ryan
1df6ff6735
* feat: Add workflow to run Go program and create PR Introduces a GitHub Actions workflow that checks out two repositories, sets up Go, installs dependencies, runs a Go program, and creates a pull request with generated documentation updates. * fix: Update workflow name and trigger Renamed the workflow to 'Feature Matrix Creator' and changed the trigger from push on main to manual workflow_dispatch. * feat: Add feature-matrix tool for ADK feature extraction Introduces a new tool under tools/feature-matrix to generate a feature support matrix for ADK runtimes by analyzing documentation. Includes Go implementation (main.go), prompt and starter markdown files, and Go module dependencies. * feat: Update feature matrix workflow to use local tool Removes checkout of the adk-docs-features repo and updates steps to use the local tools/feature-matrix directory for dependency installation and program execution. Simplifies the workflow by eliminating unnecessary repository cloning and file movement. * fix: Update feature matrix prompt and matrix content Revised the prompt to use 'Unsupported' instead of 'Planned' for features not supported, clarified disclaimer placement, and updated instructions for matrix ordering. Updated start.md to move the disclaimer and feature matrix to the top, reflect new terminology, and provide a more accurate and current feature support matrix.
2.2 KiB
Analyze the documentation for the adk project and please come up with a list of features that adk delivers. Focus on page titles and section headers to come up with that list.
Once that is done, I'd like to generate a matrix of features enabled by runtime.
Currently there are two runtimes: python (adk-python) which is the primary, and java (adk-java). But soon go (adk-go) and typescript (adk-js) will be added.
A good metric for figuring out if a feature is supported per runtime is if the sample code associated with a given feature in adk-docs includes samples in a given language.
For each matrix item showing support, please link to the code sample where you use to say that this feature is supported in the language. Use https://google.github.io/adk-docs/ as the base link. Also mkae sure to include path and page so the links will work.
Output the content in markdown.
Please double check the matrix's markdown content for validity before outputting.
Please say "Unsupported" instead of "No" when a feature is not supported, unless there is text in the documentation that makes it clear that a particular feature will not be supported in a given language, in which case, then write "no". If you mark something as know please include a link to the text that makes you make that determination. Nearest header is close enough.
Write the output as if it was going to be a page available in adk-docs. Match adk-docs style and tone.
Please always preface the content with this disclaimer markdown content after ADK Features header and becfore first paragraph:
!!! note: This content is autogenerated by Gemini, based on our documentation. It is a best effort to generate a feature matrix, but may not be 100% accurate as features can outpace documentation, or Gemini might inaccurately generate content.
Always place the feature matrix at the top of the content after the disclaimer and before the prose decription of the features.
For now omit Typescript and Go from matrix.
Pattern for building urls from markdown paths should be to replaced the .md extension with a "/".
Use the following markdown as an example of a good previous run of this content and should really only be updated if content in adk-docs has changed: