Skip to content

Conversation

@jonathannorris
Copy link
Member

Changing a link in the README.md from /technologies to /sdks

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates a documentation link to reflect a path change in the OpenFeature website structure, moving from /technologies to /sdks.

  • Updated SDK compatibility documentation link from /technologies/sdk-compatibility to /sdks/sdk-compatibility
  • Reformatted multi-line sentence about parsing the specification into separate lines

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jonathannorris, 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 addresses a documentation maintenance task by updating an outdated link within the README.md file. The change ensures that the SDK compatibility overview points to the correct and current location, improving the user experience for those seeking information on OpenFeature SDKs. A small, cosmetic formatting change was also included to enhance readability.

Highlights

  • Documentation Link Update: The SDK compatibility overview link in README.md has been updated to reflect the new path, ensuring users are directed to the correct documentation.
  • README.md Formatting: A minor formatting adjustment was made in README.md to improve the readability of the instructions for parsing the specification.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@jonathannorris jonathannorris force-pushed the docs-update-sdk-compatibility-link branch from dc18b3f to a5d40a8 Compare October 24, 2025 19:23
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly updates a link to the SDK compatibility page in the README.md. However, it also includes an unrelated formatting change. To maintain a clean and focused commit history, it's best practice to keep pull requests focused on a single logical change. I have added a comment suggesting this formatting change be reverted and submitted in a separate pull request.

@beeme1mr beeme1mr merged commit 6d7d4c6 into main Oct 27, 2025
9 of 10 checks passed
@beeme1mr beeme1mr deleted the docs-update-sdk-compatibility-link branch October 27, 2025 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants