Skip to content

Update requesting_access_to_data.md#76

Merged
clairerye merged 5 commits intomainfrom
clairerye-patch-3
Mar 18, 2026
Merged

Update requesting_access_to_data.md#76
clairerye merged 5 commits intomainfrom
clairerye-patch-3

Conversation

@clairerye
Copy link
Collaborator

new instructions for data access

new instructions for data access

Signed-off-by: Claire Rye <claire.rye@auckland.ac.nz>
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, 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 the documentation for requesting data access, shifting from a manual, form-based approach to a more integrated system managed by REMS. The changes aim to provide clearer, more current instructions for users seeking access to data, outlining the steps from browsing projects to application submission and review.

Highlights

  • Data Access Process Update: The guide for requesting data access has been significantly revised to reflect a new, streamlined application process.
  • Introduction of REMS: The Resource Entitlement Management System (REMS) is now explicitly mentioned as the platform managing all data access applications.
  • Content Modernization: Outdated direct links to specific project pages, Google Forms, and illustrative images have been removed, replaced with general browsing and exploration links.
  • Clarified Review Workflow: The post-submission process, including registration, form completion, review by the AGDR team and kaitiaki, and potential outcomes, has been detailed.

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

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 updates the documentation for requesting data access. The changes replace outdated instructions that pointed to specific projects and a Google Form with a more general process involving a discovery/exploration page and a new Resource Entitlement Management System (REMS). My review focuses on improving the clarity and correctness of the new instructions. I've pointed out some issues with broken/misleading links, typos, and inconsistencies in the new text, and suggested fixes to make the documentation easier for users to follow.

clairerye and others added 3 commits March 18, 2026 16:12
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Claire Rye <claire.rye@auckland.ac.nz>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Claire Rye <claire.rye@auckland.ac.nz>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Signed-off-by: Claire Rye <claire.rye@auckland.ac.nz>
@clairerye clairerye merged commit d6e3af2 into main Mar 18, 2026
6 checks passed
@clairerye clairerye deleted the clairerye-patch-3 branch March 18, 2026 03:14
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.

1 participant