dev: Increase DevContainer 2 to 4 CPUs, and rm extension

[vorburger]

GitHub default 2 CPU machines for Codespace are unbearably slow to work on with Maven Java projects, so bump to 4 CPUs requirement.

Also remove the "rangav.vscode-thunder-client" VSC extension (https://www.thunderclient.com) which was originally automatically added, but is not required.

[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 enhances the development environment by optimizing resource allocation for DevContainers and streamlining the VS Code extension setup. The changes aim to provide a more efficient and less resource-intensive development experience, particularly for Java projects, by ensuring adequate processing power and removing unnecessary tools.

Highlights

• DevContainer CPU Increase: The required CPU count for the DevContainer has been increased from the default 2 to 4, to improve performance for Maven Java projects.
• Extension Removal: The "rangav.vscode-thunder-client" VS Code extension, which was not required, has been removed from the DevContainer configuration.

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

Changelog

• .devcontainer/devcontainer.json
  • Removed the "rangav.vscode-thunder-client" extension from the list of installed VS Code extensions.
  • Added a "hostRequirements" section to specify a minimum of 4 CPUs for the DevContainer.

Activity

• No specific activity has been recorded for this pull request 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 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 updates the DevContainer configuration to increase the required CPUs to 4 and removes an unnecessary VS Code extension. The changes are straightforward, but I've identified two minor issues: a leftover trailing comma that could make the JSON invalid for some parsers, and a personal comment that should be removed for clarity. I've provided suggestions to address both points.