Org name changed

[pattacini]

This is due to https://github.com/orgs/robotology/discussions/730.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 implements a global update to reflect a change in the project's organizational affiliation. The core purpose is to ensure all internal and external links, documentation references, and configuration settings accurately point to the new 'mesh-iit' organization, maintaining consistency and accessibility for users and developers.

Highlights

• Organization Name Update: All references to the previous organization name, 'icub-tech-iit', have been systematically updated to the new 'mesh-iit' across the project's files.
• URL and Link Corrections: Various URLs and links within the documentation, configuration files, and source code comments have been corrected to reflect the new organization's GitHub domain and associated web properties.

Changelog

• CITATION.cff
  • Updated the project's URL to reflect the new organization name.
• README.md
  • Corrected multiple GitHub repository and documentation URLs from 'icub-tech-iit' to 'mesh-iit'.
  • Updated references to vcpkg.json and issue trackers with the new organization name.
• mkdocs.yml
  • Modified the site_url, repo_name, and repo_url to align with the new 'mesh-iit' organization.
  • Updated the documentation navigation link.
• src/creo2urdf/include/creo2urdf/Utils.h
  • Updated a GitHub issue URL in a code comment.
• src/creo2urdf/src/Creo2Urdf.cpp
  • Updated GitHub issue URLs in code comments.
• vcpkg.json
  • Updated the homepage and documentation URLs to reflect the new organization.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/dispatch-ci.yml

Activity

• No specific activity (comments, reviews, progress) has been recorded for this pull request yet.

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]

Code Review

This pull request updates the organization name from icub-tech-iit to mesh-iit. The changes have been applied to various configuration files, documentation, and source code comments. After reviewing the modifications, I have not identified any issues in the changed lines.