Skip to content

Comments

migrate video url to github#320

Merged
bebechien merged 5 commits intogoogle-gemini:mainfrom
bebechien:main
Feb 24, 2026
Merged

migrate video url to github#320
bebechien merged 5 commits intogoogle-gemini:mainfrom
bebechien:main

Conversation

@bebechien
Copy link
Collaborator

No description provided.

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @bebechien, 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 video-understanding.ipynb notebook to retrieve its sample video from a GitHub repository instead of a Google Cloud Storage bucket. This change aims to improve the reliability and accessibility of the video resource used in the notebook, along with updating the recorded execution outputs to match the new source.

Highlights

  • Video URL Migration: The video download URL in the video-understanding.ipynb notebook has been migrated from a Google Cloud Storage bucket to a GitHub raw content link, ensuring a more consistent and accessible source for the sample video.
  • Notebook Output Updates: Associated execution counts and output logs within the notebook were refreshed to reflect the new video source and the updated execution environment.
Changelog
  • docs/capabilities/vision/video-understanding.ipynb
    • Updated the video download URL to point to a GitHub raw content link.
    • Adjusted the execution count for a code cell.
    • Refreshed the wget and ffmpeg command output logs to reflect the new download source and execution environment.
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.

@bebechien bebechien merged commit c0f382f into google-gemini:main Feb 24, 2026
4 checks passed
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

The pull request successfully migrates the video download URL from Google Cloud Storage to a GitHub raw content URL, aligning with the pull request's objective. The changes in the notebook's output reflect this new source and the execution environment. While the migration to GitHub is complete, it's worth considering the long-term stability and performance implications of serving large assets directly from raw GitHub content URLs for tutorials.

],
"source": [
"!wget http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/ForBiggerBlazes.mp4 -O /content/video.mp4\n",
"!wget https://github.com/bebechien/gemma/raw/refs/heads/main/videos/ForBiggerBlazes.mp4 -O /content/video.mp4\n",
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The video asset is now sourced from a raw GitHub content URL. While this works, raw GitHub URLs are generally not designed for high-availability or high-performance content delivery and can sometimes be subject to rate limits or changes in repository structure that could break the link. For a tutorial that needs to be consistently runnable, using a more stable content delivery mechanism (like a dedicated CDN or object storage) might be more robust in the long run. However, given the PR's explicit goal to migrate to GitHub, this is noted as a potential point of fragility rather than a direct issue with the current implementation.

Copy link
Member

Choose a reason for hiding this comment

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

I've copied the video to http://storage.googleapis.com/generativeai-downloads/videos/ForBiggerBlazes.mp4

That's our team's public-facing bucket, can you update to use that instead of a GitHub link?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants