chore: align HTML settings page wording

[rrama]

Description

Made sure the main page had some of the tooltips, etc. found in the fallback page.
Also ensured the debug page had all its styles scoped correctly.

Checklist

• Tests added and all succeed
• N/A
• Regenerated mocks, etc. (make generate)
• N/A, although we should really make the script generate the debug page fresh, so we can view the changes over time on GitHub.
• Linted (make lint-fix)
• N/A, doesn't do HTML.
• README.md updated, if user-facing
• N/A
• License file updated, if new 3rd-party dependency is introduced
• N/A

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @rrama, 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 focuses on refining the user interface and preventing potential styling issues within the application's HTML pages. It enhances the main configuration page by providing more descriptive tooltips and clearer input field placeholders, thereby improving user understanding. Concurrently, it addresses a potential technical debt by meticulously scoping the CSS rules within the debug page, ensuring that its styles are isolated and do not inadvertently affect other components.

Highlights

• HTML Configuration Page Enhancements: Improved the config.html page by adding tooltips for better user guidance and updating placeholder text for clarity on input fields.
• Debug Page CSS Scoping: Ensured that all CSS styles within the debug page (scripts/config-dialog/main.go) are properly scoped under the #test-panel ID to prevent style conflicts with other parts of the application.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 improves the user experience on the settings page by adding and clarifying tooltips for several configuration options. The changes in infrastructure/configuration/template/config.html make the purpose of settings like 'Insecure (Skip SSL Verification)' and 'CLI Download Base URL' clearer to the user. Additionally, the pull request correctly scopes the CSS for the debug page within scripts/config-dialog/main.go, preventing potential style conflicts with the main application. The changes are well-implemented and align with the goals stated in the description. I have reviewed the code and found no issues.