-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Added attendee Priyanshu_Jain.md #15687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Priyanshu Jain <163391789+priyanshu4999@users.noreply.github.com>
Yay, your first pull request! 👍 A contributor will be by to give feedback soon. In the meantime, you can find updates in the #github-notifications channel in the community Slack. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @priyanshu4999, 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 introduces a new attendee, Priyanshu Jain, by adding a dedicated Markdown file. The file provides a brief self-introduction, highlighting their interest in open-source and cloud infrastructure, and listing their technical skills. This change primarily serves to document the presence and background of a new contributor or participant within the project's meeting documentation.
Highlights
- New Attendee Introduction: A new Markdown file,
Priyanshu_Jain.md
, has been added under thedocs/_meetings/2025/week-of-08-25-2025/
directory. This file serves as an introduction for Priyanshu Jain, outlining their interest in open-source and cloud infrastructure, and listing their technical proficiencies including MERN stack with TypeScript (React & Next.js), Golang, and Python.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
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 issue 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
-
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. ↩
There was a problem hiding this 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 introduces a new attendee file for Priyanshu Jain. The file provides a brief introduction and technical skills. My review focuses on improving the markdown formatting by removing unnecessary trailing whitespace, which will ensure consistent rendering across different platforms.
### Hi, I'm Priyanshu Jain | ||
|
||
I am exploring OSS and Cloud Infra, and Meshery seemed like a perfect fit for me. | ||
|
||
- MERN with TypeScript (React & Next.js) | ||
- Golang | ||
- Python | ||
|
||
**Feel free to connect with me:** [LinkedIn](https://www.linkedin.com/in/priyanshujain4999/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are trailing whitespaces on several lines in this file (1, 3, 5, 6, 7, and 9). While some Markdown parsers interpret two trailing spaces as a hard line break, this is often unintentional and can lead to inconsistent rendering. It's best practice to remove trailing whitespace for cleaner and more predictable formatting.
### Hi, I'm Priyanshu Jain | |
I am exploring OSS and Cloud Infra, and Meshery seemed like a perfect fit for me. | |
- MERN with TypeScript (React & Next.js) | |
- Golang | |
- Python | |
**Feel free to connect with me:** [LinkedIn](https://www.linkedin.com/in/priyanshujain4999/) | |
### Hi, I'm Priyanshu Jain | |
I am exploring OSS and Cloud Infra, and Meshery seemed like a perfect fit for me. | |
- MERN with TypeScript (React & Next.js) | |
- Golang | |
- Python | |
**Feel free to connect with me:** [LinkedIn](https://www.linkedin.com/in/priyanshujain4999/) |
|
🚀 Preview for commit 510f203 at: https://68b05d771e57353b90e1f128--meshery-docs-preview.netlify.app |
Thanks for your contribution to Meshery! 🎉
|
Notes for Reviewers
Signed commits