Revise OAuth login fix and consent screen instructions

[zeuslawyer]

Updated instructions for fixing OAuth login issues and updated consent screen steps.

Description

The README instructions on how to find add one's account as the test user account were outdated/incorrect.
Fix was performed directly from Github as it was only to README.

Checklist:

• [X ] My code follows the AGENTS.md guidelines (no generated google-* crates).
• I have run cargo fmt --all to format the code perfectly.
• [] I have run cargo clippy -- -D warnings and resolved all warnings.
• [] I have added tests that prove my fix is effective or that my feature works.
• [] I have provided a Changeset file (e.g. via pnpx changeset) to document my changes.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d2729a2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

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

[gemini-code-assist]

Summary of Changes

Hello, 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 refines the documentation for resolving common OAuth login problems and navigating the consent screen within the Google Cloud Platform. The updates aim to provide clearer and more accurate steps for users encountering these issues, ensuring a smoother authentication process for applications in testing mode.

Highlights

• OAuth Login Fix Instructions: The link for fixing OAuth login issues has been updated from 'OAuth consent screen' to 'Google Auth Platform Audience screen' to reflect the current Google Cloud Console navigation.
• Consent Screen Warning Guidance: Instructions for handling the 'Google hasn't verified this app' warning have been simplified, changing the guidance from clicking 'Advanced' then 'Go to (unsafe)' to simply clicking 'Continue'.

Changelog

• README.md
  • Updated the URL and steps for adding test users to fix OAuth login issues.
  • Revised the instructions for bypassing the 'Google hasn't verified this app' warning.

Activity

• The pull request includes a standard checklist for code quality, testing, and documentation.
• A section for --dry-run output is present, indicating a potential requirement for new features or commands, though no output was provided.
• No specific review comments or progress updates have been recorded yet.

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 Generative AI Prohibited Use Policy, 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 updates instructions in the README.md file for OAuth login and consent screens. The changes aim to align the documentation with the current Google Cloud Console user interface. My review identified an inconsistency where a URL was updated in the troubleshooting section but not in the manual setup instructions. I have added a comment to highlight this for correction.