Skip to content

Update Weekly_Online_Office_Hours.md#1184

Open
nishag90 wants to merge 1 commit intomainfrom
nishag90-patch-1-1
Open

Update Weekly_Online_Office_Hours.md#1184
nishag90 wants to merge 1 commit intomainfrom
nishag90-patch-1-1

Conversation

@nishag90
Copy link
Collaborator

@nishag90 nishag90 commented Mar 9, 2026

No description provided.

Signed-off-by: Nisha Ghatak <106782494+nishag90@users.noreply.github.com>
@github-actions
Copy link
Contributor

github-actions bot commented Mar 9, 2026

Test deployment successful!! (2026-03-09T19:54:47Z)
Preview available at https://callumwalley.github.io/mkdocs-demo-deploy/nesi/support-docs/nishag90-patch-1-1

Seems the following pages differ;



See all deployed demo sites

@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 embedded calendar link on the Weekly Online Office Hours documentation page. The change ensures that users are directed to the correct and current calendar for scheduling office hour sessions, improving accessibility and accuracy of information.

Highlights

  • Calendar Embed Link Updated: The embedded calendar link for weekly online office hours has been updated from a Google Calendar embed to an Outlook Office 365 calendar embed.

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

Changelog
  • docs/Getting_Started/Getting_Help/Weekly_Online_Office_Hours.md
    • Updated the iframe source URL to point to the new Outlook Office 365 calendar.
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.


Old link now gone, New calendar, fresh and bright, Meetings now found.

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.

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