Skip to content

Fix librealsense links - #426

Merged
pattacini merged 1 commit into
mesh-iit:masterfrom
martinaxgloria:fix/librealsense_link
Jan 14, 2026
Merged

Fix librealsense links#426
pattacini merged 1 commit into
mesh-iit:masterfrom
martinaxgloria:fix/librealsense_link

Conversation

@martinaxgloria

Copy link
Copy Markdown
Member

librealsense was migrated to the RealSenseAI organization (see https://github.com/realsenseai/librealsense). With this PR, the links to the repository are fixed.

@martinaxgloria martinaxgloria self-assigned this Jan 14, 2026
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @martinaxgloria, 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 updates all references to the librealsense GitHub repository across the documentation to align with its recent migration to the RealSenseAI organization. The change ensures that all installation guides and resource links are accurate and functional, directing users to the correct and current location of the project's assets and documentation.

Highlights

  • Repository Migration: Updated all librealsense GitHub repository links to reflect its migration from IntelRealSense to the realsenseai organization.
  • Documentation Accuracy: Ensured that installation instructions for Jetpack 5.x.x and 6.x.x, including links for Debian packages, building from source, and the libuvc_installation.sh script, now point to the correct repository.
  • Official Documentation Link: The link to the official librealsense documentation within the installation guide has been corrected.

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

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

Copy link
Copy Markdown
Contributor

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 aims to fix broken links to the librealsense repository after its migration to the RealSenseAI organization. The changes are mostly correct, but I've identified one link that was missed during the update. My review includes a suggestion to fix this remaining broken link.

@pattacini
pattacini merged commit c81b0a0 into mesh-iit:master Jan 14, 2026
1 check passed
@martinaxgloria
martinaxgloria deleted the fix/librealsense_link branch January 14, 2026 14:07
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