Update README to include RC

[cy245]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @cy245, I'm Gemini Code Assist¹! 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 improves the project's documentation by introducing a new section in the Shrine/README.md file. This addition aims to clarify the concept and implementation of 'Restore Credentials' within the application, detailing how they are created and utilized for seamless user authentication.

Highlights

• README Update: A new section has been added to the Shrine/README.md file.
• Restore Credentials Documentation: The newly added section provides a detailed explanation of 'Restore Credentials', covering their purpose, creation points in AuthenticationScreen.kt and RegisterPasswordScreen.kt, and how they facilitate automatic user login in AuthenticationScreen.kt.

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. ↩

[gemini-code-assist]

Code Review

This pull request adds a section on Restore Credentials to the README file. The explanation is mostly correct and provides a good overview. I've suggested a minor wording change to improve the clarity and technical accuracy of one sentence.

[gemini-code-assist]

The description of how a restore credential is created is a bit confusing and technically inaccurate. It says a function is passed to the View Model, but it's more accurate to say a View Model function is called. Also, "in to" should be "into", and using "a restore credential" instead of "this" would be clearer. I suggest rephrasing for better clarity and accuracy.

Suggested change

	new device. In Shrine, this is created in `AuthenticationScreen.kt` upon signing in successfully and
	passing the `createRestoreKey()` function in to the View Model. This is also done in
	new device. In Shrine, a restore credential is created in `AuthenticationScreen.kt` upon successful
	sign-in by calling the View Model's `createRestoreKey()` function. This is also done in

[shumelchyk]

LGTM, thanks!