Skip to content

Conversation

@leecalcote
Copy link
Member

Notes for Reviewers

  • This PR fixes #

Signed commits

  • Yes, I signed my commits.

Signed-off-by: Lee Calcote <lee.calcote@layer5.io>
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @leecalcote, 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 focuses on a minor documentation update, specifically renaming the title of the Meshery CLI contributing guidelines page to "Meshery CLI Style Guide". This change aims to provide a more accurate and descriptive title for the document, better reflecting its content which pertains to design principles and code conventions rather than general contribution steps.

Highlights

  • Documentation Update: The title of the Meshery CLI Contributing Guidelines page has been updated to Meshery CLI Style Guide to better reflect its content and purpose.
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.

@github-actions github-actions bot added the area/docs Documentation update needed label Dec 17, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the title of the CLI contributing guidelines to 'Style Guide'. While this change accurately reflects the content's purpose, the change appears incomplete. The filename contributing-guidelines.md has not been updated to match the new title, which can cause confusion. I've added a comment with a suggestion to rename the file for consistency. Additionally, please ensure your commits are signed as per the contribution guidelines.

---
layout: default
title: "Meshery CLI Contributing Guidelines"
title: "Meshery CLI Style Guide"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While changing the title to 'Meshery CLI Style Guide' is a good step, this change seems incomplete given the PR title 'Rename contributing guidelines to style guide'. The file itself has not been renamed and is still contributing-guidelines.md. For consistency and to avoid confusion, please consider renaming the file as well (e.g., to cli-style-guide.md). This would likely also require updating the permalink on line 5 and any internal links pointing to this page.

@github-actions
Copy link

@l5io
Copy link
Member

l5io commented Dec 17, 2025

@ritzorama ritzorama requested review from a team December 18, 2025 05:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/docs Documentation update needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants