Skip to content
This repository was archived by the owner on Sep 25, 2025. It is now read-only.

Conversation

@NULL204
Copy link
Member

@NULL204 NULL204 commented Sep 9, 2025

This PR updates explicit org URLs and converts absolute LICENSE links to relative form.

Org URL replacements: 13
LICENSE link conversions (blob): 1
LICENSE link conversions (raw): 0

Old base: TensoRaws
New base: EutropicAI

Relative ./LICENSE links stay correct if branches or hosts change.

Changes:
- Replaced 13 occurrence(s) of
  TensoRaws
  with
  EutropicAI
- Converted LICENSE links: blob=1, raw=0

Reason: organization rename + prefer stable relative license links.
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 @NULL204, 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 systematically updates references to the project's organizational identity and improves the robustness of internal links. The changes ensure that all project metadata, documentation, and configuration correctly point to the new organization, EutropicAI, and that the LICENSE link remains functional across different environments.

Highlights

  • Organization Name Update: All instances of the old organization name "TensoRaws" have been replaced with the new name "EutropicAI" across various configuration files, documentation, and the license.
  • Absolute URL to Relative Path Conversion: An absolute link to the LICENSE file in README.md has been converted to a relative path (./LICENSE) to ensure link validity regardless of branch or host changes.
  • Model URL Updates: Download URLs for models in ccvfi/config/drba_config.py and ccvfi/config/rife_config.py have been updated to reflect the new organization name.
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 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
Copy link

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

@Tohrusky Tohrusky merged commit c670f62 into EutropicAI:main Sep 9, 2025
0 of 12 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants