docs: update contributing.md integration test code reference to v0.23.0 tag#2197
Conversation
Summary of ChangesHello @Yuan325, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request focuses on maintaining the accuracy and relevance of the project's contributing guidelines. It ensures that external code references within the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request updates code references in CONTRIBUTING.md to point to the v0.23.0 tag instead of a specific commit hash, which is a great improvement for documentation clarity. The changes also improve link formatting consistency by removing unnecessary angle brackets.
While the changes in this PR are correct, I noticed that a few other links within CONTRIBUTING.md still point to the old commit hash. To make this update more complete, you might consider updating these links as well:
- Line 90:
[SourceConfig](https://github.com/googleapis/genai-toolbox/blob/fd300dc606d88bf9f7bba689e2cee4e3565537dd/internal/sources/sources.go#L57) - Line 98:
[Source](https://github.com/googleapis/genai-toolbox/blob/fd300dc606d88bf9f7bba689e2cee4e3565537dd/internal/sources/sources.go#L63) - Line 118:
[ToolConfig](https://github.com/googleapis/genai-toolbox/blob/fd300dc606d88bf9f7bba689e2cee4e3565537dd/internal/tools/tools.go#L61)
Updating these would ensure all code references in the document are consistent. Otherwise, the current changes look good.
….0 tag (googleapis#2197) Update links to point towards files within v0.23.0 version. There are some updates done within the function since the previous link was generated.
Update links to point towards files within v0.23.0 version. There are some updates done within the function since the previous link was generated.