Set token before connection probing

[simo-prior]

Description

Internal environments will require passing the token for all the endpoints due to auth proxies.

[CLAassistant]

All committers have signed the CLA.

[gemini-code-assist]

Summary of Changes

Hello @simo-prior, 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 addresses an authentication requirement in internal environments by adjusting the sequence of operations during client initialization. It ensures that authentication tokens are prepared prior to any network communication, which is crucial when dealing with authentication proxies that demand tokens for all endpoints, including connection probes.

Highlights

• Authentication Token Pre-fetching: The logic for retrieving and reusing an existing authentication token has been reordered to execute before the connection accessibility check. This ensures that a token is available for all endpoint interactions, including initial connection probing, which is critical for environments with authentication proxies.

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 correctly moves the token retrieval before the connection check to support authentication with auth proxies. My feedback focuses on a minor style issue where a multi-line assignment was converted to a single long line. I've suggested reverting this for better readability and consistency with the project's apparent style.

[brendan-priorlabs]

Approving now in case this is urgent, but please do consider that comment for user-friendliness!