Skip to content

Conversation

@amondnet
Copy link

@amondnet amondnet commented Jan 7, 2026

Update relative path to CONTRIBUTING.md from the plugin README to correctly point to the repository root (../../../CONTRIBUTING.md).

The previous link CONTRIBUTING.md was broken as there is no CONTRIBUTING.md file in the plugin directory.

Checklist (if applicable):

Update relative path to CONTRIBUTING.md from the plugin README
to correctly point to the repository root.
@github-actions github-actions bot added docs Improvements or additions to documentation js fix labels Jan 7, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @amondnet, 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 resolves a minor documentation issue by fixing an incorrect relative path within the Anthropic plugin's README file. The change ensures that the link to the project's contribution guidelines is functional, thereby improving navigation for potential contributors and maintaining the accuracy of the project's documentation.

Highlights

  • Documentation Fix: Corrected a broken link in the js/plugins/anthropic/README.md file that pointed to the CONTRIBUTING.md guidelines.
  • Path Correction: The relative path for the contribution guidelines link was updated from CONTRIBUTING.md to ../../../CONTRIBUTING.md to correctly reference the file at the repository root.

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

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.

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 correctly fixes a broken link to the CONTRIBUTING.md file within the Anthropic plugin's README. The updated relative path is accurate. I have provided one suggestion to use a repository-root-relative link instead, which would make the link more robust to future file location changes. Otherwise, the change is good.

## Contributing

Want to contribute to the project? That's awesome! Head over to our [Contribution Guidelines](CONTRIBUTING.md).
Want to contribute to the project? That's awesome! Head over to our [Contribution Guidelines](../../../CONTRIBUTING.md).
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 the relative path ../../../CONTRIBUTING.md is correct, it's a good practice in GitHub Markdown to use a path relative to the repository root. This makes the link more robust and less likely to break if this README file is moved in the future. Using a root-relative link like (/CONTRIBUTING.md) is a more maintainable approach.

Suggested change
Want to contribute to the project? That's awesome! Head over to our [Contribution Guidelines](../../../CONTRIBUTING.md).
Want to contribute to the project? That's awesome! Head over to our [Contribution Guidelines](/CONTRIBUTING.md).

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

Labels

docs Improvements or additions to documentation fix js

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant