[nightcityblade]

Description

Updates the stable plugins table to show that Remote Config supports Windows. Also adds the contributor entry required by the Contributor Guide.

Related Issues

Fixes #18763

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide). N/A: this is a documentation-only change with no runtime behavior.
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///). This PR updates the repository README.
• The analyzer (melos run analyze) does not report any problems on my PR. N/A: no Dart source files changed.
• I read and followed the Flutter Style Guide.
• I signed the CLA. I will complete it if the CLA check requests action.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change.
• No, this is not a breaking change.

[gemini-code-assist]

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 the 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 counterproductive. 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.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[SelaseKay]

Hi @nightcityblade, thanks for the pull request. The Windows cell should be (*) rather than ✔, matching the other Windows C++ plugins in that table. cla/google is failing, so the pull request is not mergeable.

[nightcityblade]

Thanks for the correction. Updated the Windows cell to (*) in 88ce307 so it matches the development-only footnote and the other Windows C++ plugins. I also verified the exact table row and footnote and ran git diff --check. The remaining cla/google check requires the GitHub account holder to complete Google’s CLA.

[SelaseKay]

Hi @nightcityblade, kindly sign cla.

[nightcityblade]

Acknowledged. The requested documentation correction is already in 88ce307 and all code checks are green. The remaining Google CLA is an account-level action that cannot be completed through a code change, so this PR will remain blocked until that signing step is completed separately.