Skip to content

adding file for new repo, giving access to people from research lab #262

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

Merged
merged 2 commits into from
Jun 23, 2025

Conversation

Lawproto
Copy link
Member

As per title.

@Lawproto Lawproto requested a review from pattacini as a code owner June 23, 2025 15:29
@Lawproto Lawproto had a problem deploying to outside_collaborators_environment June 23, 2025 15:29 — with GitHub Actions Error
Copy link

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

Summary of Changes

Hello @Lawproto, 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 configuration file to establish access controls for a newly defined repository, ergocub2-design-lowerarm. The primary purpose is to provision read access for specific research lab groups and an individual user, facilitating their collaboration and access to the repository's contents.

Highlights

  • New Repository Configuration: A new YAML configuration file, repos/ergocub2-design-lowerarm.yml, has been added to define access permissions for the ergocub2-design-lowerarm repository.
  • Access Provisioning: Read access has been explicitly granted to two groups, hsp-iit/sw-dev and ami-iit/mech, as well as to the individual user PasMarra for the newly configured 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.

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

@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 adds a new YAML file to define repository access permissions for the 'ergocub2-design-lowerarm' repository, granting read access to specific groups and a user. I suggested adding a description to the file for clarity.

Copy link
Member

@pattacini pattacini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Lawproto for bringing this up 👍🏻

I'd rather propose to use the proper ergocub groups as already done for example in https://github.com/icub-tech-iit/outside-collaborators/blob/master/repos/ergocub2-design-upperbody.yml.

@pattacini pattacini temporarily deployed to outside_collaborators_environment June 23, 2025 16:17 — with GitHub Actions Inactive
@pattacini pattacini merged commit fd6d7fe into icub-tech-iit:master Jun 23, 2025
1 check passed
@Lawproto
Copy link
Member Author

Lawproto commented Jun 25, 2025

I'd rather propose to use the proper ergocub groups as already done for example in https://github.com/icub-tech-iit/outside-collaborators/blob/master/repos/ergocub2-design-upperbody.yml.

@pattacini the people I am interested in are part of that group as well, so ok.

GitHub
Automatically Manage Outside Collaborators Organization-wide - icub-tech-iit/outside-collaborators

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