Skip to content

Comments

Add Vivgrid information to README#258

Open
Yoname wants to merge 1 commit intocheahjs:mainfrom
Yoname:patch-1
Open

Add Vivgrid information to README#258
Yoname wants to merge 1 commit intocheahjs:mainfrom
Yoname:patch-1

Conversation

@Yoname
Copy link

@Yoname Yoname commented Dec 16, 2025

Added Vivgrid section with model limits and request details.

Added Vivgrid section with model limits and request details.
@gemini-code-assist
Copy link

Summary of Changes

Hello @Yoname, 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 enhances the project's documentation by integrating Vivgrid into the list of free API access providers. The update includes essential information such as Vivgrid's request limits and the specific models it supports, making it easier for users to discover and utilize this new service. The primary goal is to keep the resource list comprehensive and up-to-date for the community.

Highlights

  • New Provider Added: Introduced Vivgrid as a new provider for free API access, expanding the list of available services.
  • README Update: The README.md file has been updated to include a dedicated section for Vivgrid, detailing its model limits and supported models.
  • Table of Contents: The table of contents in README.md now includes a direct link to the new Vivgrid section.
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.

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 Vivgrid as a new provider. However, it cannot be merged in its current form due to two critical issues. Firstly, it directly modifies README.md, which is an auto-generated file; changes must be made to the underlying generator script. Secondly, the provider Vivgrid appears to violate the repository's contribution guidelines by listing models that are not publicly available (e.g., GPT-5, Gemini 3.0), which suggests it may be an illegitimate service. There are also several formatting inconsistencies that should be addressed.

- [GitHub Models](#github-models)
- [Cloudflare Workers AI](#cloudflare-workers-ai)
- [Google Cloud Vertex AI](#google-cloud-vertex-ai)
- [Vivgrid](#vivgrid)

Choose a reason for hiding this comment

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

critical

This README.md file is auto-generated and should not be edited directly, as stated in the warning at the top of the file. All changes should be made by modifying the generator script (src/pull_available_models.py) or its data sources, and then running the script to update the README. Direct edits will be overwritten.

Comment on lines +315 to +331
### [Vivgrid](https://vivgrid.com)

**Limits:**

[5 requests/minute<br>no requests limits/day](https://docs.vivgrid.com/models)

- gpt-5.2-instant
- gpt-5
- gpt-5-mini
- gpt-4.1
- gpt-4o
- Gemini-3.0
- gemini-2.5-pro
- gemini-2.5-flash
- deepseek-v3.2-exp
- deepseek-v3.1
- deepseek-r1-0528

Choose a reason for hiding this comment

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

critical

The provider being added, Vivgrid, appears to violate the repository's contribution guidelines regarding legitimacy. It lists several models like gpt-5, gpt-5.2-instant, gpt-4.1, and Gemini-3.0 which have not been publicly released by their respective developers (OpenAI and Google). This suggests the service might be based on reverse-engineering or other practices that are explicitly disallowed by this repository's policy. Please refer to the contribution guidelines in the PR template and the warning note in the README.

Comment on lines +319 to +331
[5 requests/minute<br>no requests limits/day](https://docs.vivgrid.com/models)

- gpt-5.2-instant
- gpt-5
- gpt-5-mini
- gpt-4.1
- gpt-4o
- Gemini-3.0
- gemini-2.5-pro
- gemini-2.5-flash
- deepseek-v3.2-exp
- deepseek-v3.1
- deepseek-r1-0528

Choose a reason for hiding this comment

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

medium

There are a few formatting and clarity issues in this section that should be addressed for consistency with the rest of the document:

  • The limit description no requests limits/day is ambiguous. It should be rephrased for clarity, for example, as unlimited daily requests.
  • The model names are not consistently cased (e.g., Gemini-3.0 vs gemini-2.5-pro). They should follow a consistent capitalization scheme.
  • Unlike other providers in this list, the models are not hyperlinked to a page with more details.

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