-
Notifications
You must be signed in to change notification settings - Fork 6.6k
chore(language): remove markdown files from migration #13235
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
chore(language): remove markdown files from migration #13235
Conversation
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.
Hello @eapl-gemugami, 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!
Summary of Changes
This pull request focuses on cleaning up the language
directory by removing outdated and redundant Markdown files. Specifically, it removes files that point to an archived repository (returning a 404 error) and files that are already present in the root directory of the project.
Highlights
- Markdown File Removal: Removes
language/README.md
which contains a link to an archived repository. - Redundancy Elimination: Deletes
language/AUTHORING_GUIDE.md
andlanguage/CONTRIBUTING.md
as these files are already available in the root directory.
Changelog
- language/AUTHORING_GUIDE.md
- Removed the file as it duplicates content in the root directory.
- language/CONTRIBUTING.md
- Removed the file as it duplicates content in the root directory.
- language/README.md
- Removed the file because it links to an archived repository.
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 is currently in preview and 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 to provide feedback.
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.
Trivia time!
What is Markdown, and who created it?
Click here for the answer
Markdown is a lightweight markup language with plain text formatting syntax. It was created by John Gruber and Aaron Swartz.
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
The pull request aims to remove outdated and redundant Markdown files from the repository. The changes seem straightforward and address the issues described in the pull request description.
Merge Readiness
The pull request appears to be ready for merging, as it removes outdated and redundant files, aligning with the description. I am unable to directly approve the pull request, and recommend that others review and approve this code before merging.
Description
Delete Markdown files pointing to an archived repo which returned a "Not found 404".
Delete files not required in this repo, as they already are in the root directory:
language/AUTHORING_GUIDE.md
language/CONTRIBUTING.md
Checklist