Skip to content

Conversation

@WesHarrell
Copy link
Collaborator

No description provided.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @WesHarrell, I'm Gemini Code Assist1! 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 Windows Subsystem for Linux (WSL), making it more current and user-friendly. The updates clarify the purpose of WSL, simplify installation instructions by removing deprecated information, and introduce valuable optional steps for enhancing the WSL experience with tools like Windows Terminal and VS Code, ultimately providing a more comprehensive and up-to-date guide for users.

Highlights

  • WSL Description Update: The introductory description of WSL has been updated for clarity and accuracy, emphasizing its seamless integration with the Windows Desktop.
  • Streamlined Installation Guide: Outdated information regarding WSL1 vs WSL2 has been removed to simplify the installation process, focusing on the current best practices.
  • IT Department Note: A note has been added to inform users that their IT department might have disabled WSL, advising them to contact support if installation fails.
  • Ubuntu LTS Version Update: References to Ubuntu LTS versions have been updated from 20.04 to 24.04 in installation examples, reflecting the latest available versions.
  • New Optional Integrations: New optional sections have been added for installing Windows Terminal and integrating WSL with VS Code, enhancing the development environment.
  • Symlink Name Change: The suggested symbolic link name for Windows filesystems has been changed from 'WinFS' to 'Cdrive' for better clarity.

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


Windows meets Linux, Terminal opens new worlds, Code flows, fast and free.

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.

@github-actions
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants